From: Vineeth Vijayan <vneethv@linux.ibm.com>
To: cohuck@redhat.com, oberpar@linux.ibm.com
Cc: linux-s390@vger.kernel.org, farman@linux.ibm.com, fiuczy@linux.ibm.com
Subject: [RFC 0/1] Remove uevent suppression logic from css driver
Date: Tue, 24 Nov 2020 10:34:06 +0100 [thread overview]
Message-ID: <20201124093407.23189-1-vneethv@linux.ibm.com> (raw)
This RFC is a follow-up for the below mentioned thread.
https://marc.info/?l=linux-s390&m=158591045732735&w=2
As mentioned in the RFD, we tried to remove the uevent suppression
logic from the css driver. I think this would help the vfio-cww
udev-rules to bind to the subchannel before the io-subchanneli driver.
Here, the uevent is generated after,stsch() and css_sch_is_valid()
which makes sure that the subchannel is valid.
Vineeth Vijayan (1):
s390/cio: Remove uevent-suppress from css driver
drivers/s390/cio/chsc_sch.c | 5 -----
drivers/s390/cio/css.c | 19 -------------------
drivers/s390/cio/device.c | 18 ------------------
drivers/s390/cio/eadm_sch.c | 5 -----
drivers/s390/cio/vfio_ccw_drv.c | 5 -----
5 files changed, 52 deletions(-)
--
2.17.1
next reply other threads:[~2020-11-24 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 9:34 Vineeth Vijayan [this message]
2020-11-24 9:34 ` [RFC 1/1] s390/cio: Remove uevent-suppress from css driver Vineeth Vijayan
2020-11-24 13:02 ` Cornelia Huck
2020-11-25 9:40 ` Vineeth Vijayan
2020-12-07 8:09 ` Vineeth Vijayan
2020-12-08 17:30 ` Cornelia Huck
2020-12-09 12:52 ` Halil Pasic
2020-12-15 18:13 ` Cornelia Huck
2020-12-19 6:33 ` Halil Pasic
2020-12-21 15:46 ` Cornelia Huck
2020-12-21 16:51 ` Halil Pasic
2021-01-14 13:03 ` Boris Fiuczynski
2021-01-19 11:47 ` Halil Pasic
2021-01-19 11:59 ` Cornelia Huck
2021-01-19 12:18 ` Vineeth Vijayan
[not found] ` <89146a87-371a-f148-057b-d3b7ce0cc21e@linux.ibm.com>
[not found] ` <20201216130710.5aa6a933.cohuck@redhat.com>
2020-12-19 7:20 ` Halil Pasic
2020-12-21 15:52 ` Cornelia Huck
2020-12-21 17:23 ` Halil Pasic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201124093407.23189-1-vneethv@linux.ibm.com \
--to=vneethv@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=fiuczy@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox