From: Linus Torvalds <torvalds@linux-foundation.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Huiwen He <hehuiwen@kylinos.cn>,
Jerome Marchand <jmarchan@redhat.com>,
Qing Wang <wangqing7171@gmail.com>,
Shengming Hu <hu.shengming@zte.com.cn>,
Linux-MM <linux-mm@kvack.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [GIT PULL] tracing: Fixes for 7.0
Date: Fri, 6 Mar 2026 08:50:01 -0800 [thread overview]
Message-ID: <CAHk-=wi4CA=yPP-rQON_2_swS5Jd0SS4UwWbct4LdfGFyzHFRg@mail.gmail.com> (raw)
In-Reply-To: <a21ea7c3-fbdb-4ac7-8be5-0173f54890c7@kernel.org>
On Thu, 5 Mar 2026 at 10:59, David Hildenbrand (Arm) <david@kernel.org> wrote:
>
> Agreed. We could think about letting it sit a bit in -next before moving
> it to mainline.
Honestly, I doubt it would get any testing in -next. Yes, -next gets
some boot testing and maybe on a good day somebody runs LTP or some
other test suite on it, but almost nobody actually *uses* it.
I think I'll just apply this now while it's early, and see if anybody
notices. Lorenzo will apparently be shitting in the woods if they do.
Linus
next prev parent reply other threads:[~2026-03-06 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260305103941.11f1b27d@gandalf.local.home>
2026-03-05 16:44 ` Linus Torvalds
2026-03-05 16:52 ` Steven Rostedt
2026-03-05 17:00 ` David Hildenbrand (Arm)
2026-03-05 17:17 ` Linus Torvalds
2026-03-05 18:59 ` David Hildenbrand (Arm)
2026-03-06 10:33 ` Lorenzo Stoakes (Oracle)
2026-03-06 16:50 ` Linus Torvalds [this message]
2026-03-06 16:58 ` David Hildenbrand (Arm)
2026-03-05 19:07 ` Jason Gunthorpe
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='CAHk-=wi4CA=yPP-rQON_2_swS5Jd0SS4UwWbct4LdfGFyzHFRg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=david@kernel.org \
--cc=hehuiwen@kylinos.cn \
--cc=hu.shengming@zte.com.cn \
--cc=jgg@ziepe.ca \
--cc=jmarchan@redhat.com \
--cc=leon@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=wangqing7171@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