From: Johannes Berg <johannes@sipsolutions.net>
To: Ilya Maximets <i.maximets@ovn.org>, Matthieu Baerts <matttbe@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Aaron Conole <aconole@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>,
dev@openvswitch.org, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Adrian Moreno <amorenoz@redhat.com>,
Antoine Tenart <atenart@kernel.org>
Subject: Re: [PATCH v6 3/4] net: dropreason: use new __print_sym() in tracing
Date: Tue, 22 Sep 2026 11:03:26 +0200 [thread overview]
Message-ID: <6c7170af0a7cbe62573fae461b94556f850318ee.camel@sipsolutions.net> (raw)
In-Reply-To: <dca799b4-23f5-4b6f-be73-bad5a3d88007@ovn.org> (sfid-20260922_110114_464147_BE59E097)
On Tue, 2026-09-22 at 11:01 +0200, Ilya Maximets wrote:
>
> Matthieu mentioned we'll need CONFIG_TRACEPOINTS in the selftest config
> shard: tools/testing/selftests/net/openvswitch/config
Right, I was going to comment on that but then while I was writing and
testing all your emails came in and I forgot.
> Is that a new dependency or was it always there we just missed adding it
> to the config before? (it's included in the common net config, so that
> is probably the reason why CI doesn't fail)
It can't really be new, perf to capture this was always used, I'm just
changing how the output is formatted.
Perhaps better to have that as a separate fix/cleanup?
johannes
next prev parent reply other threads:[~2026-09-22 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 10:06 [PATCH v6 0/4] tracing: improve symbolic printing Johannes Berg
2026-09-21 10:06 ` [PATCH v6 1/4] tracing: add __print_sym() to replace __print_symbolic() Johannes Berg
2026-09-21 10:06 ` [PATCH v6 2/4] tracing/timer: use __print_sym() Johannes Berg
2026-09-21 10:06 ` [PATCH v6 3/4] net: dropreason: use new __print_sym() in tracing Johannes Berg
2026-09-21 22:03 ` Matthieu Baerts
2026-09-21 22:23 ` Ilya Maximets
2026-09-21 22:36 ` Johannes Berg
2026-09-21 23:20 ` Johannes Berg
2026-09-22 9:01 ` Ilya Maximets
2026-09-22 9:03 ` Johannes Berg [this message]
2026-09-22 14:36 ` Adrián Moreno
2026-09-22 15:34 ` Aaron Conole
2026-09-22 7:18 ` Antoine Tenart
2026-09-22 8:48 ` Ilya Maximets
2026-09-22 14:35 ` Adrián Moreno
2026-09-22 14:59 ` Johannes Berg
2026-09-21 10:06 ` [PATCH v6 4/4] net: drop_monitor: use drop_reason_lookup() Johannes Berg
2026-09-21 21:59 ` [PATCH v6 0/4] tracing: improve symbolic printing Jakub Kicinski
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=6c7170af0a7cbe62573fae461b94556f850318ee.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=atenart@kernel.org \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=i.maximets@ovn.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matttbe@kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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®