The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ramesh Errabolu <ramesh@linux.ibm.com>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	driver-core@lists.linux.dev,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Leon Romanovsky" <leon@kernel.org>,
	"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>,
	"Farhan Ali" <alifm@linux.ibm.com>,
	"Ramesh Errabolu" <ramesh@linux.ibm.com>
Subject: [PATCH v5 0/1] PCI: hotplug: Add support for synthesizing slot uevents
Date: Mon,  6 Jul 2026 15:02:43 -0500	[thread overview]
Message-ID: <20260706200244.91130-1-ramesh@linux.ibm.com> (raw)

Hi all,

This patch adds support for synthesizing PCI hotplug slot uevents via a
sysfs attribute.

The patch has been rebased on top of the current upstream/devel branch
and includes the feedback received during previous review rounds. The
Reviewed-by and Tested-by tags from the previous revision have been
retained.

I'd appreciate feedback on the next steps in the review and merge
process. Please let me know if any further changes are needed.

Thanks,
Ramesh Errabolu

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


             reply	other threads:[~2026-07-06 20:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 20:02 Ramesh Errabolu [this message]
2026-07-06 20:02 ` [PATCH v5 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=20260706200244.91130-1-ramesh@linux.ibm.com \
    --to=ramesh@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alifm@linux.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=driver-core@lists.linux.dev \
    --cc=gbayer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kw@linux.com \
    --cc=leon@kernel.org \
    --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