[patch 6/10] s390: enable iucv_send2way_xxx functions.
From: Ursula Braun-Krahl <braunu@de.ibm.com>
The SSL-Server of z/VM wants to use the iucv_send2way
and iucv_send2way_array function. Enable them again.
Signed-off-by: Frank Pavlic <pavlic@de.ibm.com>
[patch 4/10] s390: schedule_timeout cleanup in ctctty.
From: Domen Puncer <domen@coderock.org>
Use msleep_interruptible() instead of schedule_timeout()
to guarantee the task delays as expected.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
Signed-off-by: Maximilian Attems <janitor@sternwelten.at>
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Frank Pavlic <pavlic@de.ibm.com>
Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
[patch 3/10] s390: set online race in the lcs driver.
From: Michael Holzheu <holzheu@de.ibm.com>
There is a race between lcs_stopcard() and lcs_open_device() which
can lead to the error 'lcs: Error in starting channel, rc=-16'.
lcs_open_device() is invoked when 'ifconfig up' is called due to a
hotplug event, which is caused by register_netdev(). In parallel
lcs_stopcard() is executed. Both functions are sending lcs commands.
The second invocation fails with -EBUSY (-16) as return value.
Move invocation of register_netdev() after invocation of lcs_stopcard
to avoid the race.
Signed-off-by: Frank Pavlic <pavlic@de.ibm.com>
[patch 2/10] s390: multicast address registration in lcs.
From: Michael Holzheu <holzheu@de.ibm.com>
When setting lcs devices online you can run into an endless loop,
because the code that registers the multicast addresses uses
list_for_each_entry instead of list_for_each_entry_safe.
Signed-off-by: Frank Pavlic <pavlic@de.ibm.com>
[patch 1/10] s390: claw driver wiring.
From: Andy Richter <richtera@us.ibm.com>
claw network driver changes:
- Add an entry to the drivers/s390/net Makefile to build the claw driver.
- Add claw channel type to cu3088.
Signed-off-by: Frank Pavlic <pavlic@de.ibm.com>
An arbitrary guest must not be allowed to trigger cmm actions. Only one
specific guest namely the one that serves as the resource monitor may send cmm
messages. Add a parameter that allows to specify the guest that may send
messages. z/VMs resource manager has the name 'VMRMSVM' which is the default.
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!