Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
Date:   Mon, 11 Dec 2023 11:34:19 +0100
From:   Miquel Raynal <miquel.raynal@bootlin.com>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the nvmem tree
Message-ID: <20231211113419.327947a7@xps-13>
In-Reply-To: <20231211084841.11b2ee48@canb.auug.org.au>
References: <20231211084841.11b2ee48@canb.auug.org.au>
Organization: Bootlin
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Stephen,

sfr@canb.auug.org.au wrote on Mon, 11 Dec 2023 08:48:41 +1100:

> Hi all,
>=20
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>=20
>   05349b48e254 ("nvmem: Do not expect fixed layouts to grab a layout driv=
er")
>=20
> This is commit
>=20
>   b7c1e53751cb ("nvmem: Do not expect fixed layouts to grab a layout driv=
er")
>=20
> in Linus' tree.
>=20
> Also, please keep all the commit message tags together at the end of
> the commit message.
>=20

This is actually fine, Srinivas needs this fix in his tree for
applying other patches, but he anyway sends a big "series" to GKH at
-rc6 who finally applies the content of the nvmem-next branch.

Thanks for the reports,
Miqu=C3=A8l