public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the regulator tree
Date: Wed, 16 Oct 2024 08:55:10 +0100	[thread overview]
Message-ID: <20241016075510.GL8348@google.com> (raw)
In-Reply-To: <20241016135943.24e1fab0@canb.auug.org.au>

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

  reply	other threads:[~2024-10-16  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  2:59 linux-next: duplicate patches in the regulator tree Stephen Rothwell
2024-10-16  7:55 ` Lee Jones [this message]
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

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=20241016075510.GL8348@google.com \
    --to=lee@kernel.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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