Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32;
Date:   Tue, 17 Oct 2023 11:42:17 +0200
From:   Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
        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 patch in the samsung-krzk tree
Message-ID: <20231017094217.vwz5vfmqsbfvi3ua@pengutronix.de>
References: <20231017110118.3712e78e@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="slm22x6xvwckr345"
Content-Disposition: inline
In-Reply-To: <20231017110118.3712e78e@canb.auug.org.au>
Precedence: bulk


--slm22x6xvwckr345
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello,

On Tue, Oct 17, 2023 at 11:01:18AM +1100, Stephen Rothwell wrote:
> The following commit is also in the arm-soc tree as a different commit
> (but the same patch):
>=20
>   0da7c05d232d ("soc: samsung: exynos-chipid: Convert to platform remove =
callback returning void")
>=20
> This is commit
>=20
>   55fa358ca89f ("soc: samsung: exynos-chipid: Convert to platform remove =
callback returning void")
>=20
> in the arm-soc tree.

a few more details that I worked out for this situation, so (hopefully)
others don't have to duplicate this effort:

The commit in the samsung-krzk tree was applied by Krzysztof at Sep 28
and sent later (Oct 16) as a patch to Arnd (and others) in reply to a PR
(https://lore.kernel.org/all/20231016072911.27148-1-krzysztof.kozlowski@lin=
aro.org/)
and without further explanation.

My guess is that the patch in question wasn't applied to a topic branch
but to Krzysztof's for-next directly and so was missed to be included in
the PR. Or it was on a topic branch but as the only patch on that and so
it was sent out individually. I'd expect that 0da7c05d232d won't make it
into the mainline.

Best regards
Uwe

--=20
Pengutronix e.K.                           | Uwe Kleine-K=F6nig            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

--slm22x6xvwckr345
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmUuVvgACgkQj4D7WH0S
/k4OMggArFtYagFh1156QdoHQyQjATaHnW7oc3Vfp3bY+ZcUiUvR2PE6jglceuc1
delEwOVa6cvJz0wpd1+e/2hqQwXFYWO2ZABVFh2ezNuWm1pQOWVzufPFYHgDU8Q1
Holn8CfiL7eLOa9l+A8ESwSVpn8oLzEwTF2hgX6L65Ms3tilAlH3J2rOyFkxx1KR
Kxg16UvZ7v0T1FOMqJx+OW+7kvk90tUfhg+q5qM8Jjka85K7y1lTCOYTZS9syYTW
r8mg3GCoNtf56Xoar7SQi3LJ8pw5lAKg8QhHpsS41LrxZD9oUkO78VEAT027dggH
dMIGINXRYENJoLGDcIeiE57keYs/1Q==
=98Ju
-----END PGP SIGNATURE-----

--slm22x6xvwckr345--