From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Zheng Yejian <zhengyejian1@huawei.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
tom.zanussi@linux.intel.com
Subject: Re: [PATCH -next] tracing/histogram: Update document for KEYS_MAX size
Date: Tue, 18 Oct 2022 12:18:04 -0400 [thread overview]
Message-ID: <20221018121804.666c700a@gandalf.local.home> (raw)
In-Reply-To: <87a65tdtcw.fsf@meer.lwn.net>
On Tue, 18 Oct 2022 09:49:51 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> > Jon, do you want to tag this for stable and pull it through your tree?
>
> Sure, I can do that.
Thanks Jon!
-- Steve
prev parent reply other threads:[~2022-10-18 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 10:38 [PATCH -next] tracing/histogram: Update document for KEYS_MAX size Zheng Yejian
2022-10-18 15:31 ` Masami Hiramatsu
2022-10-18 15:35 ` Steven Rostedt
2022-10-18 15:49 ` Jonathan Corbet
2022-10-18 16:18 ` Steven Rostedt [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=20221018121804.666c700a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=tom.zanussi@linux.intel.com \
--cc=zhengyejian1@huawei.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