linux-kernel - Re: linux-next: please update the i.MX 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120111093457.af3caeabe2dbf50b70942334@canb.auug.org.au>
Date:	Wed, 11 Jan 2012 09:34:57 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Sascha Hauer <s.hauer@...gutronix.de>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: linux-next: please update the i.MX tree

Hi Sascha,

On Tue, 10 Jan 2012 09:30:20 +0100 Sascha Hauer <s.hauer@...gutronix.de> wrote:
>
> On Tue, Jan 10, 2012 at 11:52:18AM +1100, Stephen Rothwell wrote:
> > 
> > It looks like most (if not all) of the i.MX tree has been merged into the
> > arm-soc (and Linus') tree, so could you please update the i.MX tree to
> > eliminate the conflicts I am getting.
> 
> Did this. Sorry, I was not aware that there is something in this branch.

Did you push it out? I just checked and it hasn't changed. Just to be
clear, I am fetching git://git.pengutronix.de/git/imx/linux-2.6.git
branch for-next and it hasn't changed since last September.

Should I, instead, just remove that tree from linux-next and let you send
stuff just via the arm-soc (or arm)tree?
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped