From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: regulator branch mess
Date: Tue, 4 Nov 2025 18:11:09 +0200 [thread overview]
Message-ID: <aQolne8AKHXdJw0-@smile.fi.intel.com> (raw)
In-Reply-To: <aQojdTvP94aYVW4l@finisterre.sirena.org.uk>
On Tue, Nov 04, 2025 at 04:01:57PM +0000, Mark Brown wrote:
> On Tue, Nov 04, 2025 at 05:48:28PM +0200, Andy Shevchenko wrote:
> > On Tue, Nov 04, 2025 at 03:32:59PM +0000, Mark Brown wrote:
>
> > > which doesn't doesn't correspond to "thousands" of lines. I really
> > > can't tell what on earth you are talking about here.
>
> > I look at it via GitWeb [1] and that's what I see:
>
> You are not describing a concrete problem here.
The merge in your regulator tree for-6.19 branch which is
commit 9de2057bbdfb58f4d9bb1476135317cd3fe6aa52 (patch)
tree 97c34e939fd59891ab122d191ebbe8837a0010d3
regulator: pf9453: optimize PMIC PF9453 driver
contains tons of unrelated (as far as I understood the intention of _this_
merge) stuff in it.
OR
it doesn't describe the _need_ to have all that to be merged for the series
that is less than two dozens of lines changed.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-04 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 15:20 regulator branch mess Andy Shevchenko
2025-11-04 15:32 ` Mark Brown
2025-11-04 15:48 ` Andy Shevchenko
2025-11-04 15:51 ` Andy Shevchenko
2025-11-04 16:01 ` Mark Brown
2025-11-04 16:11 ` Andy Shevchenko [this message]
2025-11-04 16:18 ` Andy Shevchenko
2025-11-04 16:30 ` Mark Brown
2025-11-04 16:54 ` Andy Shevchenko
2025-11-04 17:05 ` Mark Brown
2025-11-04 17:11 ` Andy Shevchenko
2025-11-04 22:15 ` Theodore Ts'o
2025-11-05 5:24 ` Andy Shevchenko
2025-11-05 15:08 ` Theodore Ts'o
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=aQolne8AKHXdJw0-@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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