From: "Champ, Andy" <andycham@amazon.co.uk>
To: Javi Merino <javi.merino@arm.com>
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: Fri, 1 Apr 2016 12:43:27 +0000 [thread overview]
Message-ID: <1459514580691.36442@amazon.co.uk> (raw)
In-Reply-To: <20160331085858.GA22350@e104805>
Hi All,
I've added remote git://git.lwn.net/linux.git to my tree. docs-next looks to point to commit 4817ebb144ffa5a1a2bc84b89ed9655dbe6c4502, and my patch applies cleanly to that commit.
Jonathan, what problem did you have?
Regards
Andy
________________________________________
From: Javi Merino <javi.merino@arm.com>
Sent: 31 March 2016 09:58
To: Champ, Andy
Cc: Jonathan Corbet; edubezval@gmail.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 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-04-01 12:43 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
2016-04-01 12:43 ` Champ, Andy [this message]
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=1459514580691.36442@amazon.co.uk \
--to=andycham@amazon.co.uk \
--cc=corbet@lwn.net \
--cc=durgadoss.r@intel.com \
--cc=edubezval@gmail.com \
--cc=javi.merino@arm.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 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.