linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Michael Walle <mwalle@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Julien Panis <jpanis@baylibre.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org
Subject: Re: [GIT PULL] Immutable branch between MFD, Misc and Pinctrl due for the v6.17 merge window
Date: Fri, 18 Jul 2025 14:38:46 +0100	[thread overview]
Message-ID: <20250718133846.GE11056@google.com> (raw)
In-Reply-To: <b57e761b-c1f7-46fc-a1bd-c419062ceb18@sirena.org.uk>

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 [李琼斯]

  reply	other threads:[~2025-07-18 13:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 11:45 [PATCH v2 0/7] mfd: tps6594: Add TI TPS652G1 support Michael Walle
2025-06-13 11:45 ` [PATCH v2 1/7] " Michael Walle
2025-06-19 13:35   ` Lee Jones
2025-07-10  9:00   ` Lee Jones
2025-07-10  9:06     ` Michael Walle
2025-07-10  9:47       ` Lee Jones
2025-06-13 11:45 ` [PATCH v2 2/7] misc: tps6594-pfsm: Add TI TPS652G1 PMIC PFSM Michael Walle
2025-06-30  7:48   ` Arnd Bergmann
2025-06-13 11:45 ` [PATCH v2 3/7] pinctrl: pinctrl-tps6594: Add TPS652G1 PMIC pinctrl and GPIO Michael Walle
2025-06-18 11:52   ` Linus Walleij
2025-06-13 11:45 ` [PATCH v2 4/7] regulator: tps6594-regulator: remove interrupt_count Michael Walle
2025-06-13 12:06   ` Mark Brown
2025-06-13 11:45 ` [PATCH v2 5/7] regulator: tps6594-regulator: remove hardcoded buck config Michael Walle
2025-06-13 12:06   ` Mark Brown
2025-06-13 11:45 ` [PATCH v2 6/7] regulator: tps6594-regulator: refactor variant descriptions Michael Walle
2025-06-13 12:07   ` Mark Brown
2025-06-13 11:45 ` [PATCH v2 7/7] regulator: tps6594-regulator: Add TI TPS652G1 PMIC regulators Michael Walle
2025-06-13 12:07   ` Mark Brown
2025-07-02 15:30 ` [PATCH v2 0/7] mfd: tps6594: Add TI TPS652G1 support Lee Jones
2025-07-10  8:58 ` (subset) " Lee Jones
2025-07-10  9:49 ` [GIT PULL] Immutable branch between MFD, Misc and Pinctrl due for the v6.17 merge window Lee Jones
2025-07-10  9:57   ` Mark Brown
2025-07-10 10:46     ` Michael Walle
2025-07-10 11:04       ` Mark Brown
2025-07-18  7:13     ` Lee Jones
2025-07-18 13:27       ` Mark Brown
2025-07-18 13:38         ` Lee Jones [this message]
2025-07-18 14:33           ` Mark Brown
2025-07-11 17:37   ` Linus Walleij

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=20250718133846.GE11056@google.com \
    --to=lee@kernel.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jpanis@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwalle@kernel.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).