linux-kernel - Re: [GIT PULL] Immutable branch between MFD, Misc and Pinctrl due for the v6.17 merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250718133846.GE11056@google.com>
Date: Fri, 18 Jul 2025 14:38:46 +0100
From: Lee Jones <lee@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Michael Walle <mwalle@...nel.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Julien Panis <jpanis@...libre.com>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [GIT PULL] Immutable branch between MFD, Misc and Pinctrl due
 for the v6.17 merge window

On Fri, 18 Jul 2025, Mark Brown wrote:

> On Fri, Jul 18, 2025 at 08:13:44AM +0100, Lee Jones wrote:
> > On Thu, 10 Jul 2025, Mark Brown wrote:
> > > On Thu, Jul 10, 2025 at 10:49:06AM +0100, Lee Jones wrote:
> 
> > > > Immutable branch between MFD, Misc and Pinctrl due for the v6.17 merge window
> 
> > > Is there some reason you didn't also pick up the regulator patches?
> 
> > Is that a joke?  I'm going to assume that you're not serious!
> 
> There's two things here.  One is that the discussions you've linked were
> from back in April/May which was before the merge window and things only
> got applied a day or two before the merge window opened.   Then rather
> than resending after the merge window as expected whoever it was
> complained about the patches not being applied just did that with no
> further context and it didn't occur to me to look at the date and as a
> result I missed that, sorry.
> 
> The other issue is that due to the constant drip of MFD serieses getting
> resends what I'm doing I'm just glancing at the relevant patches and
> then not looking further if I've already reviewed them.  I frequently
> have no recollection of any individual series, especially if there's
> been non-trivial time since I actively looked at it.

This is bigger than these particular series.  There are more examples,
but I stopped at the three most recent ones.

For the past decade or so I've been taking cross-subsystem patch-sets
and submitting pull-requests to all other maintainers, after testing of
course.  However, more recently you have become increasingly vocal in
terms of an alternative approach, whereby I apply the set without
patches that pertain to your AoR (usually Regulators) and submit an
immutable branch for you to pull from.  I have attempted both recently
and each has received criticism, showing preference for the other.

Honestly, I don't mind which strategy we put into place.  Let's just
agree on one and go with it.

-- 
Lee Jones [李琼斯]