mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	 Danilo Krummrich <dakr@kernel.org>,
	driver-core@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] driver core: Allow the constification of device attributes
Date: Thu, 9 Apr 2026 10:47:46 +0200	[thread overview]
Message-ID: <8954dd7f-c867-4f46-9dbb-2775187d93db@t-8ch.de> (raw)
In-Reply-To: <2026040916-rascal-oink-8875@gregkh>

On 2026-04-09 07:36:09+0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 08, 2026 at 09:30:46PM +0200, Thomas Weißschuh wrote:
> > Allow device attribute to reside in read-only memory.
> > Both const and non-const attributes are handled by the utility macros
> > and attributes can be migrated one-by-one.
> > 
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> > Thomas Weißschuh (5):
> >       driver core: Delete DEVICE_ATTR_PREALLOC()
> >       driver core: Add low-level macros for device attributes
> >       driver core: stop using generic sysfs macros for device attributes
> >       driver core: Allow the constification of device attributes
> >       driver core: Constify core device attributes
> > 
> >  drivers/base/core.c    |  50 ++++++++++----------
> >  include/linux/device.h | 122 +++++++++++++++++++++++++++++++++++++------------
> >  2 files changed, 121 insertions(+), 51 deletions(-)
> > ---
> > base-commit: 6c8dfb0362732bf1e4829867a2a5239fedc592d0
> > change-id: 20260408-sysfs-const-attr-device_attr-prep-9971fb4439da
> > 
> > Best regards,
> > --  
> > Thomas Weißschuh <linux@weissschuh.net>
> > 
> > 
> 
> We still have the is_visible_const() stuff not finished yet, why not fix
> that up first?

Because I want to touch each file or subsystem as few times as
possible. So before a subsystem is migrated, the prerequisites for
all of their used features need to be there.

Currently only the prerequisites for 'struct device_attribute' and
'struct kobj_attribute' are missing. So with this series in we can start
migrating everything that is *not* using 'struct kobj_attribute'.

> And this makes me worry, how many changes are going to be needed to move
> everything over?  thousands?

Depends on the granularity of the patches. I want to do as few as
possible, but still expect a few hundred patches.


Thomas

      reply	other threads:[~2026-04-09  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 19:30 Thomas Weißschuh
2026-04-08 19:30 ` [PATCH 1/5] driver core: Delete DEVICE_ATTR_PREALLOC() Thomas Weißschuh
2026-04-08 19:30 ` [PATCH 2/5] driver core: Add low-level macros for device attributes Thomas Weißschuh
2026-04-08 19:30 ` [PATCH 3/5] driver core: stop using generic sysfs " Thomas Weißschuh
2026-04-08 19:30 ` [PATCH 4/5] driver core: Allow the constification of " Thomas Weißschuh
2026-04-08 19:30 ` [PATCH 5/5] driver core: Constify core " Thomas Weißschuh
2026-04-09  5:36 ` [PATCH 0/5] driver core: Allow the constification of " Greg Kroah-Hartman
2026-04-09  8:47   ` Thomas Weißschuh [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=8954dd7f-c867-4f46-9dbb-2775187d93db@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®