From: Marc Zyngier <maz@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
torvalds@linux-foundation.org, Arnd Bergmann <arnd@arndb.de>,
Nathan Chancellor <nathan@kernel.org>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: trace: do not generate undefsyms_base.c
Date: Tue, 21 Apr 2026 15:16:43 +0100 [thread overview]
Message-ID: <86ik9k1jqs.wl-maz@kernel.org> (raw)
In-Reply-To: <20260421100209.7535e26f@gandalf.local.home>
On Tue, 21 Apr 2026 15:02:09 +0100,
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Tue, 21 Apr 2026 11:04:55 +0100
> Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> > The code to autogenerate undefsyms_base.c in the Makefile is larger
> > than the file itself.
> >
> > Remove the "echo" indirection that creates the file, which keeps
> > the build system sane and makes it much easier to edit it if/when
> > new situations arrive.
> >
> > Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Marc beat you to it by a few minutes ;-)
>
> https://lore.kernel.org/all/20260421095446.2951646-1-maz@kernel.org/
>
> Although he didn't Cc linux-trace-kernel@vger.kernel.org :-p
>
> But anyway, it ended up in my internal Patchwork. I'll take his as they are
> both pretty much the same patch.
On the other hand, Paolo's patch has the SPDX tag on the new file,
which I forgot to add. Your call, anyway.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-04-21 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 10:04 [PATCH] kernel: trace: do not generate undefsyms_base.c Paolo Bonzini
2026-04-21 14:02 ` Steven Rostedt
2026-04-21 14:16 ` Marc Zyngier [this message]
2026-04-21 14:21 ` Paolo Bonzini
2026-04-21 19:56 ` Steven Rostedt
2026-04-21 21:51 ` Nathan Chancellor
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=86ik9k1jqs.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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 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.