linux-kernel - Zero-length ARM headers in git HEAD

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

Message-ID: <4EAB0772.40404@garzik.org>
Date:	Fri, 28 Oct 2011 15:50:10 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	LKML <linux-kernel@...r.kernel.org>
CC:	linus.walleij@...aro.org,
	Russell King <rmk+kernel@....linux.org.uk>, swarren@...dia.com,
	Olof Johansson <olof@...om.net>,
	Ben Hutchings <ben@...adent.org.uk>,
	"Arnaud Patard (Rtp)" <arnaud.patard@...-net.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Wolfram Sang <w.sang@...gutronix.de>, bs14@....com
Subject: Zero-length ARM headers in git HEAD

Gents,

In the following kernel commits,

	9c587c05d715ca8461342c2cb3b4a67036b5c22b
	ea5abbd215b749b2ff14397a47a5e65741c67bf4
	cc890cd78acd7ab03442907d354b6af34e973cb3

the file ...$platform/mach/gpio.h is replaced with an empty file.  This 
disagrees with kernel tradition and kernel makefiles, where zero length 
files are intentionally deleted when "make distclean" is executed.

As a result, git sequences such as "make distclean ; git checkout 
master" may fail, because several files are present in the index but not 
on disk, making it appear as if modifications have been made:

	$ git checkout master
	D	arch/arm/mach-lpc32xx/include/mach/gpio.h
	D	arch/arm/mach-tegra/include/mach/gpio.h
	D	arch/arm/mach-u300/include/mach/gpio.h

An update, either (a) making these files non-zero length or (b) deleting 
the files in git would be appreciated.  Reading the commit descriptions, 
it appears (a) is the correct path?

	Jeff



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