From: Javi Merino <javi.merino@arm.com>
To: "Champ, Andy" <andycham@amazon.co.uk>
Cc: Jonathan Corbet <corbet@lwn.net>,
"edubezval@gmail.com" <edubezval@gmail.com>,
"durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"leo.yan@linaro.org" <leo.yan@linaro.org>,
"kapileshwar.singh@arm.com" <kapileshwar.singh@arm.com>,
"wni@nvidia.com" <wni@nvidia.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Syntactic and factual errors in the API document
Date: Thu, 31 Mar 2016 09:58:58 +0100 [thread overview]
Message-ID: <20160331085858.GA22350@e104805> (raw)
In-Reply-To: <1459413122072.981@amazon.co.uk>
On Thu, Mar 31, 2016 at 08:32:26AM +0000, Champ, Andy wrote:
> I thought that _was_ the current kernel (not the obsolete one our chip vendor supports).
>
> Which one do you mean by current? (URL & commit ID would be great!)
You can find it in the MAINTAINERS file. I think Jon refers to
git://git.lwn.net/linux.git docs-next
Cheers,
Javi
> ________________________________________
> From: Jonathan Corbet <corbet@lwn.net>
> Sent: 31 March 2016 07:43
> To: Champ, Andy
> Cc: edubezval@gmail.com; javi.merino@arm.com; durgadoss.r@intel.com; leo.yan@linaro.org; kapileshwar.singh@arm.com; wni@nvidia.com; linux-doc@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] Syntactic and factual errors in the API document
>
> On Tue, 22 Mar 2016 12:37:25 +0000
> Andy Champ <andycham@amazon.com> wrote:
>
> > There are several places where the English in the document is syntactically
> > invalid, or unclear. There are also one or two factual errors.
>
> I went to apply this one to the docs tree, but it no longer applies to
> current kernels. Any chance of getting a respin?
>
> Thanks,
>
> jon
>
>
>
next prev parent reply other threads:[~2016-03-31 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 12:37 [PATCH] Syntactic and factual errors in the API document Andy Champ
2016-03-22 13:24 ` R, Durgadoss
2016-03-22 14:35 ` Javi Merino
2016-03-22 14:53 ` Champ, Andy
2016-03-22 16:00 ` Eduardo Valentin
2016-03-28 13:41 ` Eduardo Valentin
2016-03-31 6:43 ` Jonathan Corbet
2016-03-31 8:32 ` Champ, Andy
2016-03-31 8:58 ` Javi Merino [this message]
2016-04-01 12:43 ` Champ, Andy
2016-04-01 2:35 ` Eduardo Valentin
2016-04-01 13:42 ` Jonathan Corbet
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=20160331085858.GA22350@e104805 \
--to=javi.merino@arm.com \
--cc=andycham@amazon.co.uk \
--cc=corbet@lwn.net \
--cc=durgadoss.r@intel.com \
--cc=edubezval@gmail.com \
--cc=kapileshwar.singh@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wni@nvidia.com \
/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).