linux-kernel - Re: linux-next: manual merge of the imx-mxs tree with the arm tree

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] [day] [month] [year] [list]

Message-ID: <20140129035817.GB13518@S2101-09.ap.freescale.net>
Date:	Wed, 29 Jan 2014 11:58:19 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Russell King - ARM Linux <linux@....linux.org.uk>,
	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the imx-mxs tree with the arm tree

On Wed, Jan 29, 2014 at 01:25:13PM +1100, Stephen Rothwell wrote:
> Hi Shawn,
> 
> On Wed, 29 Jan 2014 09:18:06 +0800 Shawn Guo <shawn.guo@...aro.org> wrote:
> >
> > I will rebase my branch on v3.14-rc1 once it's out.
> 
> Um, does that mean that all that stuff is *not* destined for v3.14? ...

Yes, Stephen.  That's the case.  If it causes problem for you, you can
keep excluding my for-next branch from linux-next until I rebase it on
v3.14-rc1.

Shawn

--
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/