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>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] sysfs: finalize the constification of 'struct bin_attribute'
Date: Wed, 18 Jun 2025 12:46:23 +0200 [thread overview]
Message-ID: <c1a71cd1-3922-4f73-b441-eb9a7bc7771c@t-8ch.de> (raw)
In-Reply-To: <2025061841-vixen-smuggler-9cc4@gregkh>
On 2025-06-18 09:50:07+0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 17, 2025 at 04:06:48PM +0200, Thomas Weißschuh wrote:
> > On 2025-06-17 10:48:00+0200, Greg Kroah-Hartman wrote:
> > > On Sat, Jun 14, 2025 at 08:23:24AM +0200, Thomas Weißschuh wrote:
> > > > friendly ping. You wanted to send this to Linux at around -rc1.
> > > > The changes should now apply cleanly to mainline.
> > >
> > > I've taken the first 4 patches into driver-core-testing at the moment
> > > (will move to driver-core-next if it passes 0-day testing). The last 2
> > > I'll hold off of for the next -rc1 as I was way too late here, sorry, my
> > > fault. I blame travel, which I had to do a bunch of the past few weeks :(
> >
> > Works for me.
> >
> > On the other hand it should be possible to take all patches through the
> > normal -next process right now. This is not a flag-day conversion. The final
> > const variants are already in v6.16-rc1, so everybody can just use those.
>
> There is a flag-day in that new patches could be using the old types,
> right?
They could; but this should always the case, no?
For me a flag-day conversion means that there is no way for users to
be compatible with the old and new API at the same time.
So everything needs to happen at once.
But here users of the old API can adapt their code to be compatible
with both the old and new APIs at the same time.
Not that there are any users of the old API in -next anyways.
However if you want to stick to a out-of-cycle patch, that works for me, too.
prev parent reply other threads:[~2025-06-18 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 3:54 Thomas Weißschuh
2025-05-30 3:54 ` [PATCH v3 1/6] const_structs.checkpatch: add bin_attribute Thomas Weißschuh
2025-05-30 3:54 ` [PATCH v3 2/6] sysfs: constify internal references to 'struct bin_attribute' Thomas Weißschuh
2025-05-30 3:54 ` [PATCH v3 3/6] sysfs: treewide: switch back to bin_attribute::read()/write() Thomas Weißschuh
2025-05-30 3:54 ` [PATCH v3 4/6] sysfs: treewide: switch back to attribute_group::bin_attrs Thomas Weißschuh
2025-05-30 3:54 ` [PATCH v3 5/6] sysfs: remove bin_attribute::read_new/write_new() Thomas Weißschuh
2025-05-30 3:54 ` [PATCH v3 6/6] sysfs: remove attribute_group::bin_attrs_new Thomas Weißschuh
2025-06-14 6:23 ` [PATCH v3 0/6] sysfs: finalize the constification of 'struct bin_attribute' Thomas Weißschuh
2025-06-17 8:48 ` Greg Kroah-Hartman
2025-06-17 14:06 ` Thomas Weißschuh
2025-06-18 7:50 ` Greg Kroah-Hartman
2025-06-18 10:46 ` 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=c1a71cd1-3922-4f73-b441-eb9a7bc7771c@t-8ch.de \
--to=linux@weissschuh.net \
--cc=dakr@kernel.org \
--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®