From: Ramesh Errabolu <ramesh@linux.ibm.com>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Lukas Wunner <lukas@wunner.de>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Gerd Bayer <gbayer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Ramesh Errabolu <ramesh@linux.ibm.com>
Subject: [PATCH v2 0/1] PCI/hotplug: Add 'uevent' sysfs attribute to trigger slot events
Date: Thu, 16 Apr 2026 16:39:08 -0500 [thread overview]
Message-ID: <20260416213909.705753-1-ramesh@linux.ibm.com> (raw)
Hi all,
This is v2 of the patch adding write-only uevent
support for PCI slots. The original v1 was posted
in February 2026 and received valuable feedback from
Leon Romanovsky and others. This v2 addresses the feedback
and is rebased onto the current kernel tree.
Link to v1:
https://lore.kernel.org/all/20260225150815.81268-1-ramesh@linux.ibm.com/
Testing: Tested on s390x with multiple PCI slots
- Write-only uevent attribute is created for each slot
- Writing "add" triggers proper uevent generation
- udevadm-trigger successfully generates slot uevents
- Events are properly received by udev monitoring tools
Changes since v1 (February 2026):
- Improved commit message clarity, per reviewer feedback
- Rebased onto current kernel tree (v7.x)
Ramesh Errabolu (1):
PCI/hotplug: Add 'uevent' sysfs attribute to trigger slot events
drivers/pci/hotplug/pci_hotplug_core.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
--
2.43.0
next reply other threads:[~2026-04-16 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 21:39 Ramesh Errabolu [this message]
2026-04-16 21:39 ` [PATCH v2 1/1] PCI/hotplug: Add 'uevent' sysfs attribute to trigger slot events Ramesh Errabolu
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=20260416213909.705753-1-ramesh@linux.ibm.com \
--to=ramesh@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=gbayer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=schnelle@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