linux-kernel - Re: [PATCH] Syntactic and factual errors in the API document

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1459413122072.981@amazon.co.uk>
Date:	Thu, 31 Mar 2016 08:32:26 +0000
From:	"Champ, Andy" <andycham@...zon.co.uk>
To:	Jonathan Corbet <corbet@....net>
CC:	"edubezval@...il.com" <edubezval@...il.com>,
	"javi.merino@....com" <javi.merino@....com>,
	"durgadoss.r@...el.com" <durgadoss.r@...el.com>,
	"leo.yan@...aro.org" <leo.yan@...aro.org>,
	"kapileshwar.singh@....com" <kapileshwar.singh@....com>,
	"wni@...dia.com" <wni@...dia.com>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Syntactic and factual errors in the API document

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!)

Andy
________________________________________
From: Jonathan Corbet <corbet@....net>
Sent: 31 March 2016 07:43
To: Champ, Andy
Cc: edubezval@...il.com; javi.merino@....com; durgadoss.r@...el.com; leo.yan@...aro.org; kapileshwar.singh@....com; wni@...dia.com; linux-doc@...r.kernel.org; linux-kernel@...r.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@...zon.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