From: Andrew Morton <akpm@linux-foundation.org>
To: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Sang-Heon Jeon <ekffu200098@gmail.com>
Subject: Re: [PATCH v2 0/4] bootconfig: Reject unexpected data after null character and cleanups
Date: Sun, 13 Sep 2026 19:40:12 -0700 [thread overview]
Message-ID: <20260913194012.284e4a9a13077c5c501919bb@linux-foundation.org> (raw)
In-Reply-To: <20260912224835.4e5f73b44cee39387554cc70@kernel.org>
On Sat, 12 Sep 2026 22:48:35 +0900 Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> > > ...
> > >
> >
> > Thanks, I've updateed mm.git's mm-nonmm-unstable branch to this version,
> >
> > > This version removes redundant buffer copy in init_xbc_with_error() [2/4]
> > > and moves BOOTCONFIG_FOOTER_SIZE to include/linux/bootconfig.h[4/4].
>
> OK, anyway I'll pick this series to bootconfig/for-next.
Oh, I didn't know such a tree existed.
No probs, I'll follow my usual automatic practice: if it appears in
linux-next, I drop the mm.git copy.
Often after checking that what-you-got matches what-i-got and
if-not-why-not. I'm not a trusting soul ;)
prev parent reply other threads:[~2026-09-14 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 14:12 Masami Hiramatsu (Google)
2026-09-11 14:13 ` [PATCH v2 1/4] bootconfig: Reject unexpected data after null character Masami Hiramatsu (Google)
2026-09-11 14:13 ` [PATCH v2 2/4] tools/bootconfig: Consolidate xbc_init() to error message wrapper Masami Hiramatsu (Google)
2026-09-12 14:07 ` Sang-Heon Jeon
2026-09-11 14:13 ` [PATCH v2 3/4] bootconfig: Skip internal tree sanity checks in kernel Masami Hiramatsu (Google)
2026-09-11 14:13 ` [PATCH v2 4/4] bootconfig: Move BOOTCONFIG_FOOTER_SIZE to include/linux/bootconfig.h Masami Hiramatsu (Google)
2026-09-12 14:08 ` Sang-Heon Jeon
2026-09-11 22:59 ` [PATCH v2 0/4] bootconfig: Reject unexpected data after null character and cleanups Andrew Morton
2026-09-12 13:48 ` Masami Hiramatsu
2026-09-14 2:40 ` Andrew Morton [this message]
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=20260913194012.284e4a9a13077c5c501919bb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ekffu200098@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
/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
all inboxes | Powered by JetHome®