[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQonVNgqJI56nspA@smile.fi.intel.com>
Date: Tue, 4 Nov 2025 18:18:28 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Mark Brown <broonie@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: regulator branch mess
On Tue, Nov 04, 2025 at 06:11:09PM +0200, Andy Shevchenko wrote:
> 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.
Because "base" keyword in the series points out to the
commit 98bd8b16ae57e8f25c95d496fcde3dfdd8223d41 (tag: next-20251031)
Author: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Fri Oct 31 20:35:57 2025 +1100
Add linux-next specific files for 20251031
Signed-off-by: Stephen Rothwell <sfr@...b.auug.org.au>
And that merge did it. If you are going to send this to Linus, I believe it
will become a trouble.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists