From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <kees@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Kees Cook <keescook@chromium.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 kspp tree
Date: Wed, 31 May 2023 21:12:23 -0700 [thread overview]
Message-ID: <20230531211223.c8d8bf9f07eac1386410d13e@linux-foundation.org> (raw)
In-Reply-To: <81BE1A87-DED7-4A7C-AFB8-A5AA54D19150@kernel.org>
On Wed, 31 May 2023 19:43:32 -0700 Kees Cook <kees@kernel.org> wrote:
> On May 31, 2023 7:30:56 PM PDT, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >Hi all,
> >
> >The following commit is also in the mm-hotfixes tree as a different commit
> >(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.
>
> Andrew, should I drop this from my tree?
>
Doesn't matter, as long as we don't both drop it ;)
I wibbled over cc:stable, decided not to. I did however queue it for
6.4-rcX.
I'll drop this patch from mm-hotfixes.
next prev parent reply other threads:[~2023-06-01 4:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 2:30 linux-next: duplicate patch in the kspp tree Stephen Rothwell
2023-06-01 2:43 ` Kees Cook
2023-06-01 4:12 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 7:52 Stephen Rothwell
2025-05-09 8:48 Stephen Rothwell
2025-05-09 16:32 ` Kees Cook
2025-05-13 1:32 ` Martin K. Petersen
2025-04-22 9:44 Stephen Rothwell
2025-04-22 15:51 ` Kees Cook
2024-11-04 5:42 Stephen Rothwell
2024-11-04 6:41 ` Andrew Morton
2024-07-08 8:24 Stephen Rothwell
2024-07-08 19:20 ` Kees Cook
2024-02-28 3:02 Stephen Rothwell
2024-02-28 3:26 ` Kees Cook
2024-01-04 3:23 Stephen Rothwell
2024-01-04 3:26 ` Stephen Rothwell
2023-06-05 2:34 Stephen Rothwell
2023-01-17 4:02 Stephen Rothwell
2023-01-17 4:02 ` Stephen Rothwell
2023-01-17 13:52 ` Karol Herbst
2023-01-17 20:56 ` Stephen Rothwell
2023-01-18 20:38 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230531211223.c8d8bf9f07eac1386410d13e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.