From: patchwork-bot+netdevbpf@kernel.org
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
xiyou.wangcong@gmail.com, vaclav.zindulka@tlapnet.cz,
jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net
Subject: Re: [PATCH] tracing/net_sched: Fix tracepoints that save qdisc_dev() as a string
Date: Mon, 04 Mar 2024 09:40:26 +0000 [thread overview]
Message-ID: <170954522685.11015.14202389531025914162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240229143432.273b4871@gandalf.local.home>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 29 Feb 2024 14:34:44 -0500 you wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> I'm updating __assign_str() and will be removing the second parameter. To
> make sure that it does not break anything, I make sure that it matches the
> __string() field, as that is where the string is actually going to be
> saved in. To make sure there's nothing that breaks, I added a WARN_ON() to
> make sure that what was used in __string() is the same that is used in
> __assign_str().
>
> [...]
Here is the summary with links:
- tracing/net_sched: Fix tracepoints that save qdisc_dev() as a string
https://git.kernel.org/netdev/net/c/51270d573a8d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-04 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 19:34 [PATCH] tracing/net_sched: Fix tracepoints that save qdisc_dev() as a string Steven Rostedt
2024-03-01 19:24 ` Jamal Hadi Salim
2024-03-01 20:01 ` Steven Rostedt
2024-03-01 21:07 ` Jamal Hadi Salim
2024-03-04 9:40 ` patchwork-bot+netdevbpf [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=170954522685.11015.14202389531025914162.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=vaclav.zindulka@tlapnet.cz \
--cc=xiyou.wangcong@gmail.com \
/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