From: Ralf Baechle <ralf@linux-mips.org>
To: Michal Simek <michal.simek@petalogix.com>
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 13:19:32 +0000 [thread overview]
Message-ID: <20091123131932.GA28687@linux-mips.org> (raw)
In-Reply-To: <4B0A8841.8090905@petalogix.com>
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
Ralf
next prev parent reply other threads:[~2009-11-23 13:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 7:52 linux-next: Tree for November 23 Stephen Rothwell
2009-11-23 13:04 ` Michal Simek
2009-11-23 13:19 ` Ralf Baechle [this message]
2009-11-23 13:43 ` Michal Simek
2009-11-23 19:15 ` Randy Dunlap
2009-11-23 22:54 ` Rusty Russell
2009-11-23 23:04 ` Randy Dunlap
2009-11-23 23:36 ` Stephen Rothwell
2009-11-23 23:37 ` Randy Dunlap
2009-11-23 23:43 ` Greg KH
2009-11-23 23:44 ` Randy Dunlap
2009-11-23 23:33 ` Stephen Rothwell
2009-11-23 23:34 ` Randy Dunlap
2009-11-23 23:39 ` Greg KH
2009-11-23 23:43 ` Randy Dunlap
2009-11-23 23:38 ` Greg KH
2009-11-23 23:42 ` Randy Dunlap
2009-11-24 2:34 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-11-23 3:06 Stephen Rothwell
2010-11-23 15:43 ` Zimny Lech
2010-11-23 17:15 ` Randy Dunlap
2010-11-23 19:03 ` Zimny Lech
2010-11-23 19:04 ` Zimny Lech
2010-11-23 15:45 ` Zimny Lech
2010-11-23 16:32 ` Anca Emanuel
2010-11-23 17:11 ` Anca Emanuel
2010-11-25 5:58 ` Stephen Rothwell
2010-11-24 9:24 ` Zimny Lech
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=20091123131932.GA28687@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.