[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023060207-blouse-footwear-c804@gregkh>
Date: Fri, 2 Jun 2023 09:01:19 +0100
From: Greg KH <greg@...ah.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the char-misc tree
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@...b.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 :)
Powered by blists - more mailing lists