Skip to content
Snippets Groups Projects
Select Git revision
  • 509d97b6f91b51e180ba26ddb1e2b7f6dfa80cba
  • openEuler-1.0-LTS default protected
  • openEuler-22.09
  • OLK-5.10
  • openEuler-22.03-LTS
  • openEuler-22.03-LTS-Ascend
  • master
  • openEuler-22.03-LTS-LoongArch-NW
  • openEuler-22.09-HCK
  • openEuler-20.03-LTS-SP3
  • openEuler-21.09
  • openEuler-21.03
  • openEuler-20.09
  • 4.19.90-2210.5.0
  • 5.10.0-123.0.0
  • 5.10.0-60.63.0
  • 5.10.0-60.62.0
  • 4.19.90-2210.4.0
  • 5.10.0-121.0.0
  • 5.10.0-60.61.0
  • 4.19.90-2210.3.0
  • 5.10.0-60.60.0
  • 5.10.0-120.0.0
  • 5.10.0-60.59.0
  • 5.10.0-119.0.0
  • 4.19.90-2210.2.0
  • 4.19.90-2210.1.0
  • 5.10.0-118.0.0
  • 5.10.0-106.19.0
  • 5.10.0-60.58.0
  • 4.19.90-2209.6.0
  • 5.10.0-106.18.0
  • 5.10.0-106.17.0
33 results

22b970497

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Sebastian Ott authored and Martin Schwidefsky committed
    cbc0dd1f "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: default avatarPeter Oberparleiter <peter.oberparleiter@de.ibm.com>
    Tested-by: default avatarMichael Holzheu <holzheu@linux.vnet.ibm.com>
    Signed-off-by: default avatarSebastian Ott <sebott@linux.vnet.ibm.com>
    Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
    509d97b6
    History
    Name Last commit Last update