linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
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
Date: Mon, 23 Nov 2009 14:43:27 +0100	[thread overview]
Message-ID: <4B0A917F.8060000@petalogix.com> (raw)
In-Reply-To: <20091123131932.GA28687@linux-mips.org>

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

      reply	other threads:[~2009-11-23 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091123185232.1423c56b.sfr@canb.auug.org.au>
     [not found] ` <4B0A8841.8090905@petalogix.com>
2009-11-23 13:19   ` linux-next: Tree for November 23 Ralf Baechle
2009-11-23 13:43     ` Michal Simek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0A917F.8060000@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wuzhangjin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).