From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Horman <horms@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/4] tracing: add __print_sym() to replace __print_symbolic()
Date: Wed, 27 Mar 2024 22:24:56 +0100 [thread overview]
Message-ID: <f50b31a3328986952f4042985eb5bab66c4ed1d9.camel@sipsolutions.net> (raw)
In-Reply-To: <20240327211119.GW403975@kernel.org>
On Wed, 2024-03-27 at 21:11 +0000, Simon Horman wrote:
>
> I'm seeing some allmodconfig build problems with this applied on top of
> net-next.
> ./include/trace/stages/init.h:30: warning: "TRACE_DEFINE_SYM_FNS" redefined
> ./include/trace/stages/init.h:54: warning: "TRACE_DEFINE_SYM_LIST" redefined
Yeah, the 0-day bot reported that too, sorry about that. It needs two
lines to #undef these in init.h before their definition, just like all
other macros there. Not sure why my builds didn't show that, maybe it
doesn't affect all users.
johannes
next prev parent reply other threads:[~2024-03-27 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 19:15 [RFC PATCH v2 0/4] tracing: improve symbolic printing Johannes Berg
2024-03-26 19:15 ` [RFC PATCH v2 1/4] tracing: add __print_sym() to replace __print_symbolic() Johannes Berg
2024-03-27 21:11 ` Simon Horman
2024-03-27 21:24 ` Johannes Berg [this message]
2024-03-26 19:15 ` [RFC PATCH v2 2/4] net: dropreason: use new __print_sym() in tracing Johannes Berg
2024-03-26 19:15 ` [RFC PATCH v2 3/4] net: drop_monitor: use drop_reason_lookup() Johannes Berg
2024-03-26 19:15 ` [RFC PATCH v2 4/4] tracing/timer: use __print_sym() Johannes Berg
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=f50b31a3328986952f4042985eb5bab66c4ed1d9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.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