diff options
author | Sebastian Ott <sebott@linux.vnet.ibm.com> | 2013-01-15 18:02:01 (GMT) |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2013-01-16 14:57:54 (GMT) |
commit | 509d97b6f91b51e180ba26ddb1e2b7f6dfa80cba (patch) | |
tree | d5381a3ba2c206c91dd3ed1ae9447f12af534479 /net/wireless | |
parent | ed4f20943cd4c7b55105c04daedf8d63ab6d499c (diff) | |
download | linux-509d97b6f91b51e180ba26ddb1e2b7f6dfa80cba.tar.xz |
s390/chsc: fix SEI usage
cbc0dd1 "s390/pci: CHSC PCI support for error and availability events"
introduced a new SEI notification type as part of pci support.
The way SEI was called with nt2 and nt0 consecutive broke the nt0
stuff used for channel subsystem notifications.
The reason why this was broken with the mentioned patch is that you
cannot selectively disable type 0 notifications (so even when asked
for type 2 only, type 0 could be presented).
The way to do it is to tell SEI which types of notification you can
process and -this is the important part- look at the SEI result which
notification type you actually received.
Reviewed-by: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
Tested-by: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'net/wireless')
0 files changed, 0 insertions, 0 deletions