From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com
Subject: Re: [s390] next Feb 18: defconfig build break
Date: Thu, 19 Feb 2009 10:50:44 +0530 [thread overview]
Message-ID: <499CEC2C.1060406@in.ibm.com> (raw)
In-Reply-To: <200902190913.27653.rusty@rustcorp.com.au>
Rusty Russell wrote:
> On Thursday 19 February 2009 03:40:59 Mike Frysinger wrote:
>
>> On Wed, Feb 18, 2009 at 06:45, Stephen Rothwell wrote:
>>
>>> That would be a side effect of commit 43a47c6ca0e0b5479ae316e188a28b7e625d41e5 ("misc:strstarts") from the rr tree. Rusty cc'd.
>>>
>> breaks all Blackfin ports as well:
>>
>
> My first reaction was WTF? My second was, how did our string code become
> such a catastrophe?
>
> Sorry, I had no idea what a mess I was wading into.
>
> Here's the s390 fix:
>
Thanks Rusty. That fixes the issue.
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-02-19 5:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 8:16 linux-next: Tree for February 18 Stephen Rothwell
2009-02-18 10:29 ` [s390] next Feb 18: defconfig build break Sachin P. Sant
2009-02-18 11:45 ` Stephen Rothwell
2009-02-18 17:10 ` Mike Frysinger
2009-02-18 22:43 ` Rusty Russell
2009-02-19 5:20 ` Sachin P. Sant [this message]
2009-02-20 10:23 ` Martin Schwidefsky
2009-02-18 22:59 ` Rusty Russell
2009-02-19 1:55 ` Mike Frysinger
2009-02-19 11:40 ` Rusty Russell
2009-02-19 17:14 ` Mike Frysinger
2009-02-19 0:15 ` Rusty Russell
2009-02-19 9:51 ` Russell King
2009-02-19 11:48 ` Rusty Russell
2009-02-18 18:02 ` [PATCH] module: fix build for CONFIG_SYSFS=n Randy Dunlap
2009-02-18 18:09 ` Ingo Molnar
2009-02-18 18:35 ` [PATCH v2] " Randy Dunlap
2009-02-18 19:15 ` Ingo Molnar
2009-02-19 10:50 ` Rusty Russell
2009-02-19 7:32 ` Takashi Iwai
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=499CEC2C.1060406@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--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).