linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Driver core changes for 6.16-rc1
Date: Sat, 31 May 2025 14:25:59 +0200	[thread overview]
Message-ID: <2025053142-comprised-vocally-6c11@gregkh> (raw)
In-Reply-To: <39eaf3d6-3c69-4e06-a61e-cccc7aad578d@t-8ch.de>

On Sat, May 31, 2025 at 01:40:13PM +0200, Thomas Weißschuh wrote:
> (trimmed the CC-list)
> 
> Hi Greg,
> 
> On 2025-05-28 18:29:20+0200, Greg KH wrote:
> > On Wed, May 28, 2025 at 06:16:21PM +0200, Thomas Weißschuh wrote:
> > > On 2025-05-28 17:56:52+0200, Greg KH wrote:
> 
> <snip>
> 
> > > > 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.
> 
> <snip>
> 
> > > 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.
> 
> In case you don't see patches submitted during the merge window,
> here is the updated series:
> 
> https://lore.kernel.org/lkml/20250530-sysfs-const-bin_attr-final-v3-0-724bfcf05b99@weissschuh.net/
> 
> Based on linux-next to make sure that all changes that could go into the
> merge window are accounted for.

I saw them, thanks!  I'll look at them at the end of next week.

greg k-h

  reply	other threads:[~2025-05-31 12:26 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
2025-05-31 11:40     ` Thomas Weißschuh
2025-05-31 12:25       ` Greg KH [this message]
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=2025053142-comprised-vocally-6c11@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=thomas@t-8ch.de \
    /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;
as well as URLs for NNTP newsgroup(s).