public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: 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 09:49:51 -0600	[thread overview]
Message-ID: <87a65tdtcw.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221018113558.73790f54@gandalf.local.home>

Steven Rostedt <rostedt@goodmis.org> writes:

> On Wed, 19 Oct 2022 00:31:34 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
>> On Mon, 17 Oct 2022 10:38:06 +0000
>> Zheng Yejian <zhengyejian1@huawei.com> wrote:
>> 
>> > After commit 4f36c2d85ced ("tracing: Increase tracing map KEYS_MAX size"),
>> > 'keys' supports up to three fields.  
>> 
>> This looks good to me.
>> 
>> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Thanks Masami.
>
>> 
>> Steve, do you this this document fix should go into the stable trees?
>
> We could label it as stable. Sure.
>
> Jon, do you want to tag this for stable and pull it through your tree?

Sure, I can do that.

Thanks,

jon

  reply	other threads:[~2022-10-18 15:50 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 [this message]
2022-10-18 16:18       ` 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=87a65tdtcw.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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