From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH v2 0/2] PCI: Manage hotplug attributes through group and make slot attributes const
Date: Tue, 19 May 2026 20:15:50 +0200 [thread overview]
Message-ID: <20260519-sysfs-const-pci-hotplug-v2-0-16e90346a522@weissschuh.net> (raw)
Simplify the lifecycle management of the PCI hotplug attributes with a
'struct attribute_group' and constify instances of
'struct pci_slot_attribute'.
'struct pci_slot_attribute zpci_slot_attr_uid' is not constified yet,
as it will be constified together with the rest of the zpci subsystem.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Changes in v2:
- Add a cover letter.
- Add a note about zpci_slot_attr_uid.
- Link to v1: https://patch.msgid.link/20260514-sysfs-const-pci-hotplug-v1-0-3b0b6c6f7481@weissschuh.net
---
Thomas Weißschuh (2):
PCI: hotplug: Manage hotplug slot attributes as group
PCI: Constify slot attributes
drivers/pci/hotplug/pci_hotplug_core.c | 125 +++++++++++++--------------------
drivers/pci/pci.h | 2 +-
drivers/pci/slot.c | 14 ++--
3 files changed, 57 insertions(+), 84 deletions(-)
---
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
change-id: 20260513-sysfs-const-pci-hotplug-48b62047984e
Best regards,
--
Thomas Weißschuh <linux@weissschuh.net>
next reply other threads:[~2026-05-19 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 18:15 Thomas Weißschuh [this message]
2026-05-19 18:15 ` [PATCH v2 1/2] PCI: hotplug: Manage hotplug slot attributes as group Thomas Weißschuh
2026-05-19 18:15 ` [PATCH v2 2/2] PCI: Constify slot attributes Thomas Weißschuh
2026-05-19 19:01 ` sashiko-bot
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=20260519-sysfs-const-pci-hotplug-v2-0-16e90346a522@weissschuh.net \
--to=linux@weissschuh.net \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).