linux-kernel - Re: [PATCH] x86: boot: Fix mixed indentation in a20.c

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: <528BACCB.1090604@zytor.com>
Date:	Tue, 19 Nov 2013 10:24:11 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>, Joe Perches <joe@...ches.com>
CC:	Ingo Molnar <mingo@...nel.org>,
	Johannes Löthberg <johannes@...iasis.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: boot: Fix mixed indentation in a20.c

On 11/19/2013 10:23 AM, Borislav Petkov wrote:
> On Tue, Nov 19, 2013 at 09:48:43AM -0800, Joe Perches wrote:
>> git diff -w and git blame -w both ignore whitespace changes and can
>> help in tracking down actual modifications.
> 
> That's not the point - I don't want those commits there getting in the
> way.
> 
> If it
> 
>  * doesn't fix a real bug,
>  * doesn't improve code generation
>  * doesn't have any other positive effect on the resulting object code
> 
> then it doesn't need to be there.
> 
> Whitespace jerking off doesn't belong in the kernel.
> 

I'll take a proper cleanup, but just whitespace... just pointless churn.

	-hpa

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