linux-kernel - Re: [PATCH 00/13] UAPI header file split

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: <CAHO5Pa0NOUk=Z8SNQ9t=Oi6aU96o-JtMuAytAoXJ2v1L0ntNww@mail.gmail.com>
Date:	Tue, 24 Jul 2012 14:48:38 +0200
From:	Michael Kerrisk <mtk.manpages@...il.com>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	arnd@...db.de, tglx@...utronix.de, mingo@...nel.org,
	davej@...hat.com
Subject: Re: [PATCH 00/13] UAPI header file split

On Fri, Jul 20, 2012 at 11:56 PM, David Howells <dhowells@...hat.com> wrote:

[...]

> ===================
> IMPLEMENTING STEP 1
> ===================
>
> The patches actually posted here are the manual preparation for the UAPI split
> in step (1) above.  I haven't posted the patches that do the actual splitting
> by email as the largest of them is in excess of 120,000 lines.  However, the
> patches are available through GIT:
>
>         http://git.infradead.org/users/dhowells/linux-headers.git
>
> The patches are to be found on the uapi-split branch.  The patches posted here
> are from the base of that branch up to the uapi-prep tag; the automated split
> follows thereafter to the uapi-post-split tag.

In the uapi-split branch, there are now 44 empty Kbuild files. Was
that intended? Or, should these files rather be removed by your
patches?

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface", http://blog.man7.org/
--
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/