From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
AnishMulay <anishm7030@gmail.com>,
David Carlier <devnexen@gmail.com>
Subject: Re: [GIT PULL] tracefs: Updates for v7.1
Date: Tue, 14 Apr 2026 09:42:13 -0400 [thread overview]
Message-ID: <20260414094213.495ea0bc@robin> (raw)
In-Reply-To: <20260414075753.2a036358@robin>
On Tue, 14 Apr 2026 07:57:53 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Linus,
>
> tracefs updates for 7.1:
Hi Linus,
Hold off on pulling this. I just noticed that kernel test robot found a
set but not used variable in the code. I want to fix that before it
gets pulled in.
-- Steve
next prev parent reply other threads:[~2026-04-14 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 11:57 [GIT PULL] tracefs: Updates for v7.1 Steven Rostedt
2026-04-14 13:42 ` Steven Rostedt [this message]
2026-04-16 0:51 ` pr-tracker-bot
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=20260414094213.495ea0bc@robin \
--to=rostedt@goodmis.org \
--cc=anishm7030@gmail.com \
--cc=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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