All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	ARM <linux-arm-kernel@lists.infradead.org>,
	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 char-misc tree
Date: Fri, 2 Jun 2023 09:01:19 +0100	[thread overview]
Message-ID: <2023060207-blouse-footwear-c804@gregkh> (raw)
In-Reply-To: <CACRpkdYua8NfFYYDCpDoggu3P34DQu=QdYR+2UuqO1uL2rdkmg@mail.gmail.com>

On Fri, Jun 02, 2023 at 09:54:57AM +0200, Linus Walleij wrote:
> On Fri, Jun 2, 2023 at 5:27 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > The following commits are also in the arm-soc tree as different
> > commits (but the same patches):
> >
> >   b866e7e7f995 ("misc: sram: Generate unique names for subpools")
> >   ca3222ac4477 ("dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM")
> >
> > These are commits
> >
> >   21e5a2d10c8f ("misc: sram: Generate unique names for subpools")
> >   38bd22dac71e ("dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM")
> >
> > in the arm-soc tree.
> 
> Hm hehe I was a bit confused, one misc maintainer (Arnd) merged the patches
> to the SoC tree, and another misc maintainer (Greg) merged them to the
> actual misc tree.
> 
> My misunderstanding that this was handled through SoC like drivers/soc.
> 
> Arnd can you drop this from the SoC tree?

No need to drop them, we can keep them both, no harm :)

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	ARM <linux-arm-kernel@lists.infradead.org>,
	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 char-misc tree
Date: Fri, 2 Jun 2023 09:01:19 +0100	[thread overview]
Message-ID: <2023060207-blouse-footwear-c804@gregkh> (raw)
In-Reply-To: <CACRpkdYua8NfFYYDCpDoggu3P34DQu=QdYR+2UuqO1uL2rdkmg@mail.gmail.com>

On Fri, Jun 02, 2023 at 09:54:57AM +0200, Linus Walleij wrote:
> On Fri, Jun 2, 2023 at 5:27 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > The following commits are also in the arm-soc tree as different
> > commits (but the same patches):
> >
> >   b866e7e7f995 ("misc: sram: Generate unique names for subpools")
> >   ca3222ac4477 ("dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM")
> >
> > These are commits
> >
> >   21e5a2d10c8f ("misc: sram: Generate unique names for subpools")
> >   38bd22dac71e ("dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM")
> >
> > in the arm-soc tree.
> 
> Hm hehe I was a bit confused, one misc maintainer (Arnd) merged the patches
> to the SoC tree, and another misc maintainer (Greg) merged them to the
> actual misc tree.
> 
> My misunderstanding that this was handled through SoC like drivers/soc.
> 
> Arnd can you drop this from the SoC tree?

No need to drop them, we can keep them both, no harm :)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-06-02  8:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  3:26 linux-next: duplicate patches in the char-misc tree Stephen Rothwell
2023-06-02  3:26 ` Stephen Rothwell
2023-06-02  7:54 ` Linus Walleij
2023-06-02  7:54   ` Linus Walleij
2023-06-02  8:01   ` Greg KH [this message]
2023-06-02  8:01     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2023-08-07  5:44 Stephen Rothwell
2023-08-07  6:40 ` Greg KH
2023-11-29  1:24 Stephen Rothwell
2023-11-29  1:24 ` Stephen Rothwell
2023-11-29  9:26 ` Greg KH
2023-11-29  9:26   ` Greg KH
2024-01-08  3:02 Stephen Rothwell
2024-01-08  7:54 ` Greg KH

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=2023060207-blouse-footwear-c804@gregkh \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.