Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230602132654.4497f896@canb.auug.org.au>
In-Reply-To: <20230602132654.4497f896@canb.auug.org.au>
From:   Linus Walleij <linus.walleij@linaro.org>
Date:   Fri, 2 Jun 2023 09:54:57 +0200
Message-ID: <CACRpkdYua8NfFYYDCpDoggu3P34DQu=QdYR+2UuqO1uL2rdkmg@mail.gmail.com>
Subject: Re: linux-next: duplicate patches in the char-misc tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Greg KH <greg@kroah.com>, 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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Jun 2, 2023 at 5:27=E2=80=AFAM 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?

Yours,
Linus Walleij