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  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:	Fri, 8 Aug 2014 19:55:52 +0530
From:	Jassi Brar <>
To:	Stephen Rothwell <>
Cc:	lkml <>,
	Arnd Bergmann <>, Mark Brown <>,
	Grant Likely <>,
	Mollie Wu <>,
	Tetsuya Takinishi <>,
	Andy Green <>
Subject: Re: Request to include Mailbox tree in linux-next

On 8 August 2014 09:59, Stephen Rothwell <> wrote:
> Hi Jassi,
> On Wed, 6 Aug 2014 12:25:49 +0530 Jassi Brar <> wrote:
>>  The framework for Mailbox has undergone 10 revisions over the last
>> one year, which has garnered support in the form of 'Reviewed-by' and
>> 'looks good enough to be merged in this window' from people in the CC
>> list.
>>   Could you please add it to linux-next?
>> Tree:       git://
>> Branch:   mailbox-for-3.17
>> Contact:  Jassi Brar <>
> This is really late for v3.17.  The purpose of linux-next is to
> discover interactions between trees before they are pulled into Linus'
> tree and to do some cross architecture build checking.  Adding a tree
> during the merge window is not very helpful to that.
> However if this is really going to be merged by Linus before v3.17-rc1,
> I will add it on Monday, OK?
The patchset was deemed ready enough for this merge window. However
some late nitpicks and bikeshedding discussions ate time and my
confidence to send a pull request to Linus. Upon Mark's suggestion
(and the right thing to do) I wanted the patchset to live the cycle in
 Sorry, I messed up by calling it for-3.17. It should have been for-3.18.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists