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;
Date:   Wed, 31 May 2023 19:43:32 -0700
From:   Kees Cook <kees@kernel.org>
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Kees Cook <keescook@chromium.org>,
        Andrew Morton <akpm@linux-foundation.org>
CC:     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 kspp tree
User-Agent: K-9 Mail for Android
In-Reply-To: <20230601123056.59b281c8@canb.auug.org.au>
References: <20230601123056.59b281c8@canb.auug.org.au>
Message-ID: <81BE1A87-DED7-4A7C-AFB8-A5AA54D19150@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On May 31, 2023 7:30:56 PM PDT, Stephen Rothwell <sfr@canb=2Eauug=2Eorg=2Ea=
u> wrote:
>Hi all,
>
>The following commit is also in the mm-hotfixes tree as a different commi=
t
>(but the same patch):
>
>  f7223ccc138b ("string: use __builtin_memcpy() in strlcpy/strlcat")
>
>This is commit
>
>  0af9b29c6efd ("string: use __builtin_memcpy() in strlcpy/strlcat")
>
>in the mm-hotfixes tree=2E

Andrew, should I drop this from my tree?


--=20
Kees Cook