linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>,
	Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	saiprakash.ranjan@codeaurora.org, nachukannan@gmail.com,
	rdunlap@infradead.org
Subject: Re: [PATCH v3 0/3] docs: ftrace: Fix minor issues in the doc
Date: Fri, 3 Jan 2020 17:34:33 -0500	[thread overview]
Message-ID: <20200103223433.GB189259@google.com> (raw)
In-Reply-To: <20200103114828.15581051@gandalf.local.home>

On Fri, Jan 03, 2020 at 11:48:28AM -0500, Steven Rostedt wrote:
> On Tue, 24 Dec 2019 19:05:38 -0500
> "Frank A. Cancio Bello" <frank@generalsoftwareinc.com> wrote:
> 
> > I didn't want to be pushy with these minor fixes but occur to me
> > now that, even all seem to be clear in the latest version of the
> > RFC (v2) related to these fixes, a clean patchset could be expected
> > after such RFC. So here we go:
> > 
> > Clarifies the RAM footprint of buffer_size_kb without getting into
> > implementation details.
> > 
> > Fix typos and a small notation mistakes in the doc.
> > 
> 
> Jon,
> 
> Can you take these in your tree?
> 
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>

thanks,

 - Joel

> 
> Thanks!
> 
> -- Steve

      reply	other threads:[~2020-01-03 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25  0:05 [PATCH v3 0/3] docs: ftrace: Fix minor issues in the doc Frank A. Cancio Bello
2019-12-25  0:06 ` [PATCH v3 1/3] docs: ftrace: Clarify the RAM impact of buffer_size_kb Frank A. Cancio Bello
2019-12-25  0:06 ` [PATCH v3 2/3] docs: ftrace: Fix typos Frank A. Cancio Bello
2019-12-25  0:06 ` [PATCH v3 3/3] docs: ftrace: Fix small notation mistake Frank A. Cancio Bello
2020-01-03 16:48 ` [PATCH v3 0/3] docs: ftrace: Fix minor issues in the doc Steven Rostedt
2020-01-03 22:34   ` Joel Fernandes [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=20200103223433.GB189259@google.com \
    --to=joel@joelfernandes.org \
    --cc=corbet@lwn.net \
    --cc=frank@generalsoftwareinc.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nachukannan@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=saiprakash.ranjan@codeaurora.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).