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 20:03:01 +0530 From: Jassi Brar <jaswinder.singh@...aro.org> To: Russell King - ARM Linux <linux@....linux.org.uk> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Tetsuya Takinishi <t.takinishi@...fujitsu.com>, Mollie Wu <mollie.wu@...aro.org>, Arnd Bergmann <arnd@...db.de>, Mark Brown <broonie@...aro.org>, lkml <linux-kernel@...r.kernel.org>, Andy Green <andy.green@...aro.org>, Grant Likely <grant.likely@...aro.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: Request to include Mailbox tree in linux-next On 8 August 2014 16:00, Russell King - ARM Linux <linux@....linux.org.uk> wrote: > On Fri, Aug 08, 2014 at 02:29:12PM +1000, Stephen Rothwell 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. > > +1. > > The same goes for any tree which is part of linux-next. > > Having a tree in linux-next carries with it the responsibility that the > tree owner abides by the kernel development cycle, which includes > respecting the moratorium on merging new development into branch(es) > which are part of linux-next during an actively open merge window. > I wasn't aware that any new subsystem must live at least one cycle in linux-next, I submitted it for inclusion just because someone suggested that as the next best thing to merging this cycle. Thanks -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