public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
* linux-next: duplicate patches in the regulator tree
@ 2024-10-16  2:59 Stephen Rothwell
  2024-10-16  7:55 ` Lee Jones
  0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2024-10-16  2:59 UTC (permalink / raw)
  To: Mark Brown, Liam Girdwood, Lee Jones
  Cc: Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

Hi all,

The following commits are also in the mfd tree as different commits
(but the same patches):

  d7a5f27342a8 ("mfd: sec-core: add s2dos05 support")
  ef9690c04f3b ("dt-bindings: mfd: add samsung,s2dos05")

These are commits

  59d9022639ed ("mfd: sec-core: Add support for the Samsung s2dos05")
  1d6e7612a129 ("dt-bindings: mfd: Add support for the samsung,s2dos05")

in the mfd tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: linux-next: duplicate patches in the regulator tree
  2024-10-16  2:59 linux-next: duplicate patches in the regulator tree Stephen Rothwell
@ 2024-10-16  7:55 ` Lee Jones
  2024-10-16 11:33   ` Mark Brown
  0 siblings, 1 reply; 6+ messages in thread
From: Lee Jones @ 2024-10-16  7:55 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Mark Brown, Liam Girdwood, Linux Kernel Mailing List,
	Linux Next Mailing List

On Wed, 16 Oct 2024, Stephen Rothwell wrote:

> Hi all,
> 
> The following commits are also in the mfd tree as different commits
> (but the same patches):
> 
>   d7a5f27342a8 ("mfd: sec-core: add s2dos05 support")
>   ef9690c04f3b ("dt-bindings: mfd: add samsung,s2dos05")

And these ones do not follow the style expected by the subsystem.

Mark can you please remove these without reverting and further dirtying
MFD's history please?  One little rebase isn't going to hurt in the long
run. :)

> These are commits
> 
>   59d9022639ed ("mfd: sec-core: Add support for the Samsung s2dos05")
>   1d6e7612a129 ("dt-bindings: mfd: Add support for the samsung,s2dos05")
> 
> in the mfd tree.
> 
> -- 
> Cheers,
> Stephen Rothwell



-- 
Lee Jones [李琼斯]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: linux-next: duplicate patches in the regulator tree
  2024-10-16  7:55 ` Lee Jones
@ 2024-10-16 11:33   ` Mark Brown
  2024-10-16 13:09     ` Lee Jones
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2024-10-16 11:33 UTC (permalink / raw)
  To: Lee Jones
  Cc: Stephen Rothwell, Liam Girdwood, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On Wed, Oct 16, 2024 at 08:55:10AM +0100, Lee Jones wrote:
> On Wed, 16 Oct 2024, Stephen Rothwell wrote:

> > The following commits are also in the mfd tree as different commits
> > (but the same patches):

> >   d7a5f27342a8 ("mfd: sec-core: add s2dos05 support")
> >   ef9690c04f3b ("dt-bindings: mfd: add samsung,s2dos05")

> And these ones do not follow the style expected by the subsystem.

> Mark can you please remove these without reverting and further dirtying
> MFD's history please?  One little rebase isn't going to hurt in the long
> run. :)

There's additional stuff on top of them now and I'm not clear that the
regulator patch would build without the MFD.  I don't understand why you
said to apply the patches after I'd reviewed the regulator patch,
usually you insist on waiting until all other subsystems have reviewed
before applying the MFD cores :(

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: linux-next: duplicate patches in the regulator tree
  2024-10-16 11:33   ` Mark Brown
@ 2024-10-16 13:09     ` Lee Jones
  2024-10-22 20:03       ` Mark Brown
  0 siblings, 1 reply; 6+ messages in thread
From: Lee Jones @ 2024-10-16 13:09 UTC (permalink / raw)
  To: Mark Brown
  Cc: Stephen Rothwell, Liam Girdwood, Linux Kernel Mailing List,
	Linux Next Mailing List

On Wed, 16 Oct 2024, Mark Brown wrote:

> On Wed, Oct 16, 2024 at 08:55:10AM +0100, Lee Jones wrote:
> > On Wed, 16 Oct 2024, Stephen Rothwell wrote:
> 
> > > The following commits are also in the mfd tree as different commits
> > > (but the same patches):
> 
> > >   d7a5f27342a8 ("mfd: sec-core: add s2dos05 support")
> > >   ef9690c04f3b ("dt-bindings: mfd: add samsung,s2dos05")
> 
> > And these ones do not follow the style expected by the subsystem.
> 
> > Mark can you please remove these without reverting and further dirtying
> > MFD's history please?  One little rebase isn't going to hurt in the long
> > run. :)
> 
> There's additional stuff on top of them now and I'm not clear that the
> regulator patch would build without the MFD.  I don't understand why you
> said to apply the patches after I'd reviewed the regulator patch,
> usually you insist on waiting until all other subsystems have reviewed
> before applying the MFD cores :(

I said to apply the regulator patch because it looked like it didn't
have any dependencies.  The latter part was my mistake as now I see that
it did have deps.

-- 
Lee Jones [李琼斯]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: linux-next: duplicate patches in the regulator tree
  2024-10-16 13:09     ` Lee Jones
@ 2024-10-22 20:03       ` Mark Brown
  2024-10-25  8:51         ` Lee Jones
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2024-10-22 20:03 UTC (permalink / raw)
  To: Lee Jones
  Cc: Stephen Rothwell, Liam Girdwood, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 259 bytes --]

On Wed, Oct 16, 2024 at 02:09:24PM +0100, Lee Jones wrote:

> I said to apply the regulator patch because it looked like it didn't
> have any dependencies.  The latter part was my mistake as now I see that
> it did have deps.

I've now dropped those patches.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: linux-next: duplicate patches in the regulator tree
  2024-10-22 20:03       ` Mark Brown
@ 2024-10-25  8:51         ` Lee Jones
  0 siblings, 0 replies; 6+ messages in thread
From: Lee Jones @ 2024-10-25  8:51 UTC (permalink / raw)
  To: Mark Brown
  Cc: Stephen Rothwell, Liam Girdwood, Linux Kernel Mailing List,
	Linux Next Mailing List

On Tue, 22 Oct 2024, Mark Brown wrote:

> On Wed, Oct 16, 2024 at 02:09:24PM +0100, Lee Jones wrote:
> 
> > I said to apply the regulator patch because it looked like it didn't
> > have any dependencies.  The latter part was my mistake as now I see that
> > it did have deps.
> 
> I've now dropped those patches.

Thanks Mark, I appreciate that.

-- 
Lee Jones [李琼斯]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2024-10-25  8:51 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-16  2:59 linux-next: duplicate patches in the regulator tree Stephen Rothwell
2024-10-16  7:55 ` Lee Jones
2024-10-16 11:33   ` Mark Brown
2024-10-16 13:09     ` Lee Jones
2024-10-22 20:03       ` Mark Brown
2024-10-25  8:51         ` Lee Jones

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox