From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tom Zanussi <zanussi@kernel.org>,
lixinhai.lxh@gmail.com,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix events.rst section numbering
Date: Mon, 25 May 2020 13:40:49 -0600 [thread overview]
Message-ID: <20200525134049.1b56e132@lwn.net> (raw)
In-Reply-To: <20200522083741.7d489e91@gandalf.local.home>
On Fri, 22 May 2020 08:37:41 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 18 May 2020 13:29:24 -0500
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > The in-kernel trace event API should have its own section, and the
> > duplicate section numbers need fixing as well.
> >
> > Signed-off-by: Tom Zanussi <zanussi@kernel.org>
>
> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>
> Jon,
>
> Care to take this in your tree?
Done.
jon
prev parent reply other threads:[~2020-05-25 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <90ea854dfb728390b50ddf8a8675238973ee014a.camel@kernel.org>
2020-05-22 12:37 ` [PATCH] tracing: Fix events.rst section numbering Steven Rostedt
2020-05-25 19:40 ` Jonathan Corbet [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=20200525134049.1b56e132@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixinhai.lxh@gmail.com \
--cc=rostedt@goodmis.org \
--cc=zanussi@kernel.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).