From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Stuart Hayes" <stuart.w.hayes@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"David E. Box" <david.e.box@linux.intel.com>,
"Naveen Krishna Chatradhi" <naveenkrishna.chatradhi@amd.com>,
"Carlos Bilbao" <carlos.bilbao.osdev@gmail.com>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] platform/x86: Constify 'struct bin_attribute'
Date: Thu, 12 Dec 2024 16:47:16 +0200 [thread overview]
Message-ID: <173401483637.7675.4916640925263412084.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20241202-sysfs-const-bin_attr-pdx86-v1-0-9ab204c2a814@weissschuh.net>
On Mon, 02 Dec 2024 20:38:31 +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 removed after the tree-wide transition to
> const struct bin_attribute.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/5] platform/x86: dell: dcdbas: Constify 'struct bin_attribute'
commit: f05a99b0d5f16bb82d91f602ade9a2f199c5abde
[2/5] platform/x86: dell_rbu: Constify 'struct bin_attribute'
commit: e7bcc60c87369c22dfd5e3f13c0aac58a7a3e1d9
[3/5] platform/x86/intel/sdsi: Constify 'struct bin_attribute'
commit: b5a3e35615948ab5faf773d4e5a0206020403538
[4/5] platform/x86/intel/pmt: Constify 'struct bin_attribute'
commit: 75e76075f2df25ed4e726b722aeb3ed1afd4b12a
[5/5] platform/x86/amd/hsmp: Constify 'struct bin_attribute'
commit: 2c62a6ed6fe5e084d3ef47d07087088c2e718290
--
i.
prev parent reply other threads:[~2024-12-12 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 19:38 Thomas Weißschuh
2024-12-02 19:38 ` [PATCH 1/5] platform/x86: dell: dcdbas: " Thomas Weißschuh
2024-12-02 19:38 ` [PATCH 2/5] platform/x86: dell_rbu: " Thomas Weißschuh
2024-12-02 19:38 ` [PATCH 3/5] platform/x86/intel/sdsi: " Thomas Weißschuh
2024-12-02 19:38 ` [PATCH 4/5] platform/x86/intel/pmt: " Thomas Weißschuh
2024-12-02 19:38 ` [PATCH 5/5] platform/x86/amd/hsmp: " Thomas Weißschuh
2024-12-19 14:59 ` Chatradhi, Naveen Krishna
2025-01-02 21:36 ` Carlos Bilbao
2024-12-12 14:47 ` Ilpo Järvinen [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=173401483637.7675.4916640925263412084.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stuart.w.hayes@gmail.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
Powered by JetHome