linux-kernel - Re: linux-next: duplicate patches in the kspp and kbuild trees

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2016 09:39:43 -0700
From:	Kees Cook <keescook@...gle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Michal Marek <mmarek@...e.cz>,
	Linux-Next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Emese Revfy <re.emese@...il.com>
Subject: Re: linux-next: duplicate patches in the kspp and kbuild trees

On Tue, Jun 14, 2016 at 7:13 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Michal,
>
> On Tue, 14 Jun 2016 15:01:42 +0200 Michal Marek <mmarek@...e.cz> wrote:
>>
>> I won't :). Kees, are you going to keep the patch in your tree and send
>> it to Linus once kbuild is in? Or shall I take it (which would
>> temporarily result in another duplication...).
>
> Or Kees could send you a pull request ...

My head hurts. :) How about this: since a pull request would (I think)
end up pulling the other unrelated kspp patches, how about you take
the patch into kbuild, and once it's there, I'll just remove it from
my tree (since it's on top).

-Kees

-- 
Kees Cook
Chrome OS & Brillo Security