From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] ftrace/documentation: Fix RST C code blocks
Date: Wed, 18 Nov 2020 09:24:32 -0700 [thread overview]
Message-ID: <20201118092432.1407b900@lwn.net> (raw)
In-Reply-To: <20201118105127.4a7b02ef@gandalf.local.home>
On Wed, 18 Nov 2020 10:51:27 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 18 Nov 2020 10:35:02 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
> >
> > Some C code in the ftrace-users.rst document is missing RST C block
> > annotation, which has to be added.
> >
> > Link: https://lore.kernel.org/r/20201116173502.392a769c@canb.auug.org.au
> >
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> >
>
> Jon,
>
> You want to take this through your tree?
The changes that created the warning in the first place are in the ftrace
tree, right? So it seems that the fix should be there as well; it won't
apply to the docs tree.
Thanks,
jon
next prev parent reply other threads:[~2020-11-18 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201116173502.392a769c@canb.auug.org.au>
2020-11-16 17:43 ` linux-next: build warning after merge of the ftrace tree Steven Rostedt
2020-11-16 19:24 ` Jonathan Corbet
2020-11-16 20:25 ` Steven Rostedt
2020-11-16 20:29 ` Jonathan Corbet
2020-11-16 20:35 ` Steven Rostedt
2020-11-18 15:35 ` [PATCH] ftrace/documentation: Fix RST C code blocks Steven Rostedt
2020-11-18 15:51 ` Steven Rostedt
2020-11-18 16:24 ` Jonathan Corbet [this message]
2020-11-18 16:26 ` Steven Rostedt
2020-11-18 16:28 ` Jonathan Corbet
2020-11-18 16:44 ` 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=20201118092432.1407b900@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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).