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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 8 Aug 2014 19:55:52 +0530 From: Jassi Brar <jaswinder.singh@...aro.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: lkml <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Arnd Bergmann <arnd@...db.de>, Mark Brown <broonie@...aro.org>, Grant Likely <grant.likely@...aro.org>, Mollie Wu <mollie.wu@...aro.org>, Tetsuya Takinishi <t.takinishi@...fujitsu.com>, Andy Green <andy.green@...aro.org> Subject: Re: Request to include Mailbox tree in linux-next On 8 August 2014 09:59, Stephen Rothwell <sfr@...b.auug.org.au> wrote: > Hi Jassi, > > On Wed, 6 Aug 2014 12:25:49 +0530 Jassi Brar <jaswinder.singh@...aro.org> 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://git.linaro.org/landing-teams/working/fujitsu/integration.git >> Branch: mailbox-for-3.17 >> Contact: Jassi Brar <jaswinder.singh@...aro.org> > > 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 linux-next. Sorry, I messed up by calling it for-3.17. It should have been for-3.18. Regards, -Jassi -- 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/
Powered by blists - more mailing lists