linux-kernel - Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp

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]

Date:	Fri, 6 Mar 2009 10:55:23 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Daniel Walker <dwalker@...o99.com>
cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Yinghai Lu <yinghai@...nel.org>, <mingo@...hat.com>,
	<hpa@...or.com>, <linux-kernel@...r.kernel.org>,
	<ebiederm@...ssion.com>, <akpm@...ux-foundation.org>,
	<gregkh@...e.de>, <tglx@...utronix.de>, <sarah.a.sharp@...el.com>,
	<mingo@...e.hu>, <linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp

On Fri, 6 Mar 2009, Daniel Walker wrote:

> On Fri, 2009-03-06 at 09:57 -0500, Alan Stern wrote:
> 
> > It is _not_ diehard, at least not according to Linus.  He has posted a 
> > couple of messages expressing his opinion that overall readability is 
> > more important than sticking rigidly to 80 columns.
> 
> My experience has been that anyone sending over 80 columns is sure to
> get slammed, just like with this document patch. So when I say it's die
> hard that's what I mean. Plus we have the checkpatch clean phenomenon.
> So Linus may not care but everyone else on this list does seem to care..

Well, I wouldn't have said anything if you ran over by only a few 
characters.  But your line was 97 characters long!

Alan Stern


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/