linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
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 11:26:51 -0500	[thread overview]
Message-ID: <20201118112651.0b1c9944@gandalf.local.home> (raw)
In-Reply-To: <20201118092432.1407b900@lwn.net>

On Wed, 18 Nov 2020 09:24:32 -0700
Jonathan Corbet <corbet@lwn.net> wrote:

> > 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.

Bah, I forgot the report was on linux-next and not mainline.

OK, I'll take it, but can you give an ack?

-- Steve

  reply	other threads:[~2020-11-18 16:27 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
2020-11-18 16:26               ` Steven Rostedt [this message]
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=20201118112651.0b1c9944@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).