From: Rusty Russell <rusty@rustcorp.com.au>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 30 (Blackfin string failures again)
Date: Tue, 31 Mar 2009 12:48:14 +1030 [thread overview]
Message-ID: <200903311248.14413.rusty@rustcorp.com.au> (raw)
In-Reply-To: <8bd0f97a0903301726j536da9aciaf9eb5e9a7afff5@mail.gmail.com>
On Tuesday 31 March 2009 10:56:40 Mike Frysinger wrote:
> On Mon, Mar 30, 2009 at 05:01, Stephen Rothwell wrote:
> > The rr tree lost 8 conflicts.
>
> was the Blackfin changes related to the string updates lost or
> something ? the March 30 tree brought in these failures again ...
Sorry, you're right. I dropped all the arch-specific stuff, I should
have kept that since it had your tested-by.
I'll send to Linus now.
Rusty.
next prev parent reply other threads:[~2009-03-31 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 0:26 linux-next: Tree for March 30 (Blackfin string failures again) Mike Frysinger
2009-03-31 2:18 ` Rusty Russell [this message]
2009-03-31 2:20 ` [PATCH] blackfin: allow allow usage of string functions in linux/string.h Rusty Russell
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=200903311248.14413.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vapier.adi@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).