All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Valdis.Kletnieks@vt.edu, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] doc: brief user documentation for completion
Date: Thu, 19 Feb 2015 20:04:49 +0100	[thread overview]
Message-ID: <20150219190449.GA11889@gmail.com> (raw)
In-Reply-To: <20150219153603.GA8069@opentech.at>


* Nicholas Mc Guire <der.herr@hofr.at> wrote:

> On Thu, 19 Feb 2015, Jonathan Corbet wrote:
> 
> > On Thu, 19 Feb 2015 14:29:33 +0100
> > Nicholas Mc Guire <der.herr@hofr.at> wrote:
> > 
> > > thanks for the detailed review notes
> > > 
> > > will give it another run regarding locking and context - I obviously need a 
> > > rerun regarding context and locking my self.
> > 
> > Note that the document went upstream last week, so it would be best to
> > get changes as a patch against that version.
>
> for review I do think it would be best to send it out as 
> a full text - once the content is acked no issue with 
> sending it out as a patch to the current version.

That would be fine to me. You could do both: send the full 
text, attach the diff at the end.

Thanks,

	Ingo

      reply	other threads:[~2015-02-19 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  7:01 [PATCH v4] doc: brief user documentation for completion Nicholas Mc Guire
2015-01-30 18:20 ` Jonathan Corbet
2015-02-18 22:47 ` Ingo Molnar
2015-02-19 13:29   ` Nicholas Mc Guire
2015-02-19 14:56     ` Jonathan Corbet
2015-02-19 15:36       ` Nicholas Mc Guire
2015-02-19 19:04         ` Ingo Molnar [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=20150219190449.GA11889@gmail.com \
    --to=mingo@kernel.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=corbet@lwn.net \
    --cc=der.herr@hofr.at \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.