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

Date:	Tue, 26 Mar 2013 23:32:40 +0000
From:	David Howells <dhowells@...hat.com>
To:	Michal Marek <mmarek@...e.cz>
Cc:	dhowells@...hat.com, Andrew Morton <akpm@...ux-foundation.org>,
	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

Michal Marek <mmarek@...e.cz> wrote:

> >>> I want to know whether I should extend my patch to remove include/Kbuild
> >>> and any refs to it.
> >>
> >> make headers_install starts at include/uapi, so include/Kbuild is not
> >> needed. And new exported headers end up in inclde/uapi, so there will
> >> probably not be need for include/Kbuild in the future either. IMO, just
> >> remove it.
> > 
> > That's not all Kbuild does.  It also handles autogenerated headers.
> 
> That's true. But include/generated is handled by the main Makefile
> directly as well.

But there are generated header files that aren't so handled - though those are
only currently to be found in arch/.  I don't mind removing it, it's just that
I don't want to preclude anyone's use of it.

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