Message-ID: <4B0A917F.8060000@petalogix.com>
Date: Mon, 23 Nov 2009 14:43:27 +0100
From: Michal Simek <michal.simek@petalogix.com>
Reply-To: michal.simek@petalogix.com
User-Agent: Thunderbird 2.0.0.22 (X11/20090625)
MIME-Version: 1.0
To: Ralf Baechle <ralf@linux-mips.org>
CC: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org,
       LKML <linux-kernel@vger.kernel.org>, Wu Zhangjin <wuzhangjin@gmail.com>,
       linux-mips@linux-mips.org
Subject: Re: linux-next: Tree for November 23
References: <20091123185232.1423c56b.sfr@canb.auug.org.au> <4B0A8841.8090905@petalogix.com> <20091123131932.GA28687@linux-mips.org>
In-Reply-To: <20091123131932.GA28687@linux-mips.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1021
Lines: 30

Ralf Baechle wrote:
> On Mon, Nov 23, 2009 at 02:04:01PM +0100, Michal Simek wrote:
> 
>>> The microblaze tree still has a build failure for which I reverted a
>>> commit.
>>>
>>> The mips tree gained a conflict against the microblaze tree.
>> It is problem which is caused one my ftrace patch. MIPS ftrace  
>> implementation was first that's why I should solve it. It is easy to fix.
>> I just need to know where mips/mips-for-linux-next branch is.
> 
> Gitweb:  http://www.linux-mips.org/git?p=upstream-sfr.git;a=summary
> Git:     git://www.linux-mips.org/pub/scm/upstream-sfr.git

Thanks,
Michal

> 
>   Ralf 


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/