linux-kernel - Re: linux-next: build failure after merge of the final tree (security tree related)

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: <CABqD9haMbVKn=cKuE75hSQ1YG9FgnzDhAaGUhTvk0kvJS8MGGg@mail.gmail.com>
Date:	Mon, 16 Apr 2012 10:44:09 -0500
From:	Will Drewry <wad@...omium.org>
To:	Eric Paris <eparis@...hat.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	James Morris <jmorris@...ei.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Kees Cook <keescook@...omium.org>
Subject: Re: linux-next: build failure after merge of the final tree (security
 tree related)

On Mon, Apr 16, 2012 at 10:34 AM, Eric Paris <eparis@...hat.com> wrote:
> On Mon, 2012-04-16 at 10:32 -0500, Will Drewry wrote:
>
>> Thanks for this, and the other two fixes!  I'll pull together a patch
>> fixing up the other call sites.  My past revisions had avoided this by
>> using a new symbol, and I totally forgot to touch these up in the last
>> round.
>>
>> What's the best way to submit the clean up -- against the security-next tree?
>>
>> Thanks and sorry for the noise!
>
> Just send fixes to James and they will get picked up by Stephen the day
> after he commits them to security-next.

Cool - thanks!
--
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/