From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kees Cook <kees@kernel.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: Sun, 3 Nov 2024 22:41:16 -0800 [thread overview]
Message-ID: <20241103224116.85465356eb415b9d4e5a3459@linux-foundation.org> (raw)
In-Reply-To: <20241104164255.62f42928@canb.auug.org.au>
On Mon, 4 Nov 2024 16:42:55 +1100 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):
>
> a508ef4b1dcc ("lib: string_helpers: silence snprintf() output truncation warning")
>
> This is commit
>
> 136dd147cdca ("lib: string_helpers: fix potential snprintf() output truncation")
>
> in the mm-hotifxes-unstable branch of the mm-hotfixes tree.
um, OK, unsure how string_helpers are a hardening thing (more than
anything else could be) but whatevs.
The v2 patch appears to address James's v1 comments so I'll remove this
from mm.git.
next prev parent reply other threads:[~2024-11-04 6:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 5:42 linux-next: duplicate patch in the kspp tree Stephen Rothwell
2024-11-04 6:41 ` 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-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-06-01 2:30 Stephen Rothwell
2023-06-01 2:43 ` Kees Cook
2023-06-01 4:12 ` Andrew Morton
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=20241103224116.85465356eb415b9d4e5a3459@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kees@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox