From: Greg KH <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] Driver core changes for 6.16-rc1
Date: Wed, 28 May 2025 18:29:20 +0200 [thread overview]
Message-ID: <2025052822-cavity-mortality-07d2@gregkh> (raw)
In-Reply-To: <35e4b33f-d9e4-41d6-8a47-644fda5b1b7f@t-8ch.de>
On Wed, May 28, 2025 at 06:16:21PM +0200, Thomas Weißschuh wrote:
> Hi Greg,
>
> On 2025-05-28 17:56:52+0200, Greg KH wrote:
> > The following changes since commit 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3:
> >
> > Linux 6.15-rc6 (2025-05-11 14:54:11 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-6.16-rc1
> >
> > for you to fetch changes up to 071d8e4c2a3b0999a9b822e2eb8854784a350f8a:
> >
> > kernfs: Relax constraint in draining guard (2025-05-21 14:23:13 +0200)
> >
> > ----------------------------------------------------------------
> > Driver core changes for 6.16-rc1
> >
> > Here are the driver core / kernfs changes for 6.16-rc1.
> >
> > Not a huge number of changes this development cycle, here's the summary
> > of what is included in here:
> > - kernfs locking tweaks, pushing some global locks down into a per-fs
> > image lock
> > - rust driver core and pci device bindings added for new features.
>
> > - sysfs const work for bin_attributes. This churn should now be
> > completed for those types of attributes
>
> This is missing the switch away and removal of the transitional
> struct members, "read_new", "write_new" and "bin_attrs_new".
> These are the actually churny changes.
>
> I have a branch with those, based on current linux-next/master, at
> https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/sysfs-const-bin_attr-final
>
> (Has not yet passed 0day, but earlier versions this week did)
>
> Do you want me to resubmit it to you? Now or shortly before the end of
> the merge window?
Ah, yes, those are still in my "to apply after -rc1 is out" queue, sorry
about that. And yes, I'll be glad to take updated versions as things
have changed.
thanks,
greg k-h
next prev parent reply other threads:[~2025-05-28 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 15:56 [GIT PULL] Driver core changes for 6.16-rc1 Greg KH
2025-05-28 16:16 ` Thomas Weißschuh
2025-05-28 16:29 ` Greg KH [this message]
2025-05-31 11:40 ` Thomas Weißschuh
2025-05-31 12:25 ` Greg KH
2025-05-29 16:42 ` pr-tracker-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=2025052822-cavity-mortality-07d2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thomas@t-8ch.de \
--cc=torvalds@linux-foundation.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