From: Ingo Molnar <mingo@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Nicholas Mc Guire <hofrat@osadl.org>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
Peter Zijlstra <peterz@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: completion: context, scope and language fixes
Date: Fri, 27 Mar 2015 08:56:37 +0100 [thread overview]
Message-ID: <20150327075637.GD4587@gmail.com> (raw)
In-Reply-To: <20150326112557.37602355@lwn.net>
* Jonathan Corbet <corbet@lwn.net> wrote:
> On Fri, 20 Feb 2015 12:28:48 -0500
> Nicholas Mc Guire <hofrat@osadl.org> wrote:
>
> > This hopfully address all of the issues Ingo Molnar <mingo@kernel.org> noted
> > in https://lkml.org/lkml/2015/2/18/690.
>
> This looks OK to me, modulo some small English quibbles. Ingo, does this
> satisfy your concerns?
I wasn't Cc:-ed to the patch and it wasn't Cc:-ed to lkml either :-(
(It would be very useful if documentation update patches were Cc:-ed
to the maintainers of the affected subsystem, to double check things
and so.)
Thanks,
Ingo
next prev parent reply other threads:[~2015-03-27 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 17:28 [PATCH] doc: completion: context, scope and language fixes Nicholas Mc Guire
2015-03-26 17:25 ` Jonathan Corbet
2015-03-27 7:56 ` Ingo Molnar [this message]
2015-03-27 9:46 ` Peter Zijlstra
2015-03-27 10:11 ` Ingo Molnar
2015-03-27 10:51 ` Nicholas Mc Guire
2015-03-27 11:12 ` Ingo Molnar
2015-03-27 11:10 ` Ingo Molnar
2015-03-27 16:20 ` Jonathan Corbet
2015-03-27 16:21 ` [PATCH 1/2] " Jonathan Corbet
2015-03-27 16:22 ` [PATCH 2/2] docs/completion.txt: Various tweaks and corrections Jonathan Corbet
2015-03-29 7:00 ` [PATCH] doc: completion: context, scope and language fixes Ingo Molnar
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=20150327075637.GD4587@gmail.com \
--to=mingo@kernel.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=corbet@lwn.net \
--cc=hofrat@osadl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.