Linux Trace Kernel
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Sang-Heon Jeon <ekffu200098@gmail.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH v2 2/4] tools/bootconfig: Consolidate xbc_init() to error message wrapper
Date: Tue, 13 Oct 2026 21:23:51 -0700	[thread overview]
Message-ID: <20261013212351.ce16d411abeb7e710eed5157@linux-foundation.org> (raw)
In-Reply-To: <1dcf2ee8-02f7-41af-b1f4-bff3a16a2c90@leemhuis.info>

On Wed, 14 Oct 2026 06:04:52 +0200 Thorsten Leemhuis <linux@leemhuis.info> wrote:

> On 9/11/26 16:13, Masami Hiramatsu (Google) wrote:
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> > Use init_xbc_with_error() for all bootconfig initialization in the
> > bootconfig tool instead of showing errors in different way.
> > 
> > This simplifies the code logic and make it easy to maintain.
> > 
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> 
> Masami, Andrew, this patch is now twice in -next:
> 
> e732d7c18d4d6a ("tools/bootconfig: consolidate xbc_init() to error
> message wrapper") [merged via: "9eae8e94e61f20 ("Merge branch
> 'mm-nonmm-stable' of
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm")"; next-20261012]
> 
> 78715511921cc8 ("tools/bootconfig: Consolidate xbc_init() to error
> message wrapper") [merged via: "71ee85976d09e8 ("Merge branch 'for-next'
> of
> https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git")";
> next-20261013]

OK, thanks, I'll drop the mm.git copy.

I was surprised to see bootconfig patches in the linux-trace tree, but
it seems that's where they're hosted.


  reply	other threads:[~2026-10-14  4:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 14:12 [PATCH v2 0/4] bootconfig: Reject unexpected data after null character and cleanups 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-10-14  4:04   ` Thorsten Leemhuis
2026-10-14  4:23     ` Andrew Morton [this message]
2026-10-14 12:51       ` Steven Rostedt
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

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=20261013212351.ce16d411abeb7e710eed5157@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=ekffu200098@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=mhiramat@kernel.org \
    --cc=regressions@lists.linux.dev \
    /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