public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Logan Gunthorpe <logang@deltatee.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/4] PCI: Constify 'struct bin_attribute'
Date: Tue, 3 Dec 2024 15:32:13 -0600	[thread overview]
Message-ID: <20241203213213.GA2965613@bhelgaas> (raw)
In-Reply-To: <20241202-sysfs-const-bin_attr-pci-v1-0-c32360f495a7@weissschuh.net>

On Mon, Dec 02, 2024 at 08:02:56PM +0100, Thomas Weißschuh wrote:
> The sysfs core now allows instances of 'struct bin_attribute' to be
> moved into read-only memory. Make use of that to protect them against
> accidental or malicious modifications.
> 
> The usage of read_new/write_new/bin_attrs_new is a transition mechanism
> and will be reverted after the transition is complete.
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>

Applied to pci/constify for v6.14, thanks.

Logan, I converted your response at
https://lore.kernel.org/all/003d2d13-13be-4f05-80f8-61e14ddb9c83@deltatee.com/
to include "Reviewed-by".

Let me know if that's not what you intended.

> ---
> Thomas Weißschuh (4):
>       PCI/sysfs: Constify 'struct bin_attribute'
>       PCI/VPD: Constify 'struct bin_attribute'
>       PCI/P2PDMA: Constify 'struct bin_attribute'
>       PCI/ACPI: Constify 'struct bin_attribute'
> 
>  drivers/pci/hotplug/acpiphp_ibm.c |  6 +++---
>  drivers/pci/p2pdma.c              |  6 +++---
>  drivers/pci/pci-sysfs.c           | 42 +++++++++++++++++++--------------------
>  drivers/pci/vpd.c                 | 14 ++++++-------
>  4 files changed, 34 insertions(+), 34 deletions(-)
> ---
> base-commit: e70140ba0d2b1a30467d4af6bcfe761327b9ec95
> change-id: 20241201-sysfs-const-bin_attr-pci-be2425e1a856
> 
> Best regards,
> -- 
> Thomas Weißschuh <linux@weissschuh.net>
> 

      parent reply	other threads:[~2024-12-03 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 19:02 [PATCH 0/4] PCI: Constify 'struct bin_attribute' Thomas Weißschuh
2024-12-02 19:02 ` [PATCH 1/4] PCI/sysfs: " Thomas Weißschuh
2024-12-02 19:02 ` [PATCH 2/4] PCI/VPD: " Thomas Weißschuh
2024-12-02 19:02 ` [PATCH 3/4] PCI/P2PDMA: " Thomas Weißschuh
2024-12-02 19:07   ` Logan Gunthorpe
2024-12-02 19:03 ` [PATCH 4/4] PCI/ACPI: " Thomas Weißschuh
2024-12-10 18:23   ` Rafael J. Wysocki
2024-12-03 21:32 ` Bjorn Helgaas [this message]

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=20241203213213.GA2965613@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=logang@deltatee.com \
    --cc=rafael@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