linux-kernel - Re: [PATCH] UAPI: Remove empty Kbuild files

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:	Tue, 26 Mar 2013 13:18:28 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Howells <dhowells@...hat.com>
Cc:	torvalds@...ux-foundation.org, arnd@...db.de,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] UAPI: Remove empty Kbuild files

On Tue, 26 Mar 2013 17:48:53 +0000 David Howells <dhowells@...hat.com> wrote:

> Remove empty Kbuild files as they cause problems with the patch program which
> removes files that become empty.
> 
> Should I also remove include/Kbuild as that now does nothing?  Or should it be
> left as an anchor just in case we want it in future?

I think that if the build system created it, a `make clean' or `make
mproper' should rub it out again.  Ideally a `make mrproper' will give
you a tree which is identical to a freshly-untarred kernel.org tarball
(yes?).

Which reminds me of my email which you're still hiding from ;)
Shouldn't a `make mrproper' undo the effects of `make headers_install'
by wiping ./usr/include/?

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