linux-kernel - Re: Whitespace cleanups in drm/i915

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] [day] [month] [year] [list]

Date:	Fri, 16 Sep 2011 18:01:02 -0700
From:	Ben Widawsky <ben@...dawsk.net>
To:	"Keith Packard" <keithp@...thp.com>
Cc:	airlied@...il.com, Akshay Joshi <me@...hayjoshi.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org
Subject: Re: Whitespace cleanups in drm/i915

On Thu, 15 Sep 2011 18:37:33 -0700
"Keith Packard" <keithp@...thp.com> wrote:

> 
> I've got this nice patch from Akshay Joshi that removes almost all of
> the checkpatch.pl warnings from drm/i915. If I don't merge it now,
> it's going to go stale and be useless; if I merge it only to
> drm-intel-next, it will be the source of endless conflicts.
> 
> However, it's a huge patch (yes, the code was rather sloppy), and
> doesn't exactly fit into the "critical patches only please" mode of
> the current stage of 3.1 development.
> 
> I've checked the patch very carefully, using the obvious git diff -b
> to make sure it really doesn't touch anything but whitespace, but also
> using objdump -s to compare the output of the compiler. There were no
> differences found with git-diff -b. The only differences found by
> objdump are two whitespace changes in some debug output messages in
> intel_bios.c.
> 
> I think I have three choices:
> 
>  1) merge the patch and expect complaints from upstream
> 
>  2) thank Akshay for his good intentions, discard the patch and hope
>     that he feels motivated enough to do it all over again in time for
>     the 3.2 merge window.
> 
>  3) thank Akshay for his good intentions and leave the code as-is,
>     forever to ease back-porting of fixes to older kernel versions.
> 
> Frankly, if we're ever going to merge whitespace fixups, this would
> be a pretty darn good time; drm-intel-fixes and drm-intel-next are
> in-sync as I haven't started pulling 3.2 code into -next.
> 

Not that you asked for a vote, but I vote either 1, or 3. In that order.
Let's either do it now, or never, and have the code slowly migrate over time
(kind of like Daniel said).

My only concern is the 80 characters per line rule. I'd hate to see some of
those nice readable lines go just because it's > 80.

Ben
--
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/