linux-kernel - Re: [PATCH] include/linux/regmap.h: fix a couple of typos

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: <20140109111850.GF31886@sirena.org.uk>
Date:	Thu, 9 Jan 2014 11:18:50 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	Laszlo Papp <lpapp@....org>, linux-doc@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] include/linux/regmap.h: fix a couple of typos

On Wed, Jan 08, 2014 at 06:43:20PM -0800, Randy Dunlap wrote:
> On 01/08/14 17:46, Laszlo Papp wrote:

> > I still do not get what point you are trying to make. Could you please
> > provide evidence? Because really, this is the usage I have seen in
> > projects out there all around, including the majority of the linux
> > kernel.

> I am used to seeing e.g. and i.e. always followed by a comma when they are
> used to begin a sentence.  However, I just checked and some online style
> guides say to omit the comma and some say to use it, and we (Linux kernel)
> don't really have a writing style guide to look at.  I think that makes it
> up to the maintainer to decide what is acceptable.

More generally they're just abbreviations for the latin for for example
and that is so (to a reasonable approximation) get used in the same way.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)