linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jesper Dangaard Brouer <hawk@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	bpf@vger.kernel.org, Jonathan Lemon <jonathan.lemon@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH] xdp: Remove unused mem_return_failed event
Date: Fri, 30 May 2025 18:18:13 -0700	[thread overview]
Message-ID: <20250530181813.1024eec5@kernel.org> (raw)
In-Reply-To: <20250530121638.35106c15@gandalf.local.home>

On Fri, 30 May 2025 12:16:38 -0400 Steven Rostedt wrote:
> > Acked-by: Jesper Dangaard Brouer <hawk@kernel.org>  
> 
> Thanks. Will this go through the networking tree or should I just take it?

If you're planning to send it to Linus in this MW, still, go for it:
Acked-by: Jakub Kicinski <kuba@kernel.org>
If you mean to keep it in your -next tree for next MW I think we should
take it to avoid conflict noise. But our -next tree is closed during MW
per linux-next preferences.

IOW please take it if you wanna ship it now, otherwise please repost
after MW?

  reply	other threads:[~2025-05-31  1:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 20:05 [PATCH] xdp: Remove unused mem_return_failed event Steven Rostedt
2025-05-30  6:51 ` Jesper Dangaard Brouer
2025-05-30 16:16   ` Steven Rostedt
2025-05-31  1:18     ` Jakub Kicinski [this message]
2025-05-31 20:15       ` Steven Rostedt

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=20250530181813.1024eec5@kernel.org \
    --to=kuba@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hawk@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jonathan.lemon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --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;
as well as URLs for NNTP newsgroup(s).