linux-kernel - Re: [GIT PULL] Disintegrate the User API from the kernel headers

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, 2 Oct 2012 17:22:51 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	David Howells <dhowells@...hat.com>
Cc:	torvalds@...l.org, arnd@...db.de, hpa@...or.com,
	alan@...rguk.ukuu.org.uk, fengguang.wu@...el.com,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Disintegrate the User API from the kernel headers

Hi David,

On 1 October 2012 22:05, David Howells <dhowells@...hat.com> wrote:
> Could you please pull this tree at the _end_ of this merge window?
>
> The patches therein extract the Userspace API bits from the various header
> files named in the Kbuild files and separate them out into their own files.
> The original files are then given #includes to the new files.
>
> Each new file appears in a subdirectory under either include/uapi/ or
> arch/x/include/uapi/ that corresponds to the subdirectory containing that file
> under include/ or arch/x/include/.
...
> NOTE!  These patches may need regenerating if the header files change too much
> during the remainder of the merge window.  This can mostly be handled
> automatically as the disintegration procedure is scripted.

There is arm64 that got merged, so its headers need splitting as well.
I'm happy to send a pull request myself just for arm64 if you give me
the script, otherwise you can run you script again close to -rc1 (and
I'll test it).

Thanks.

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