From: Mike Frysinger <vapier.adi@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
linux-mm@kvack.org, Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: linux-next: build failure after merge of the final tree
Date: Tue, 24 May 2011 00:10:35 -0400 [thread overview]
Message-ID: <BANLkTim-zRShhy49d7yn5WTJYzR6A2DtZQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTine2kobQA8TkmtiuXdKL=07NCo2vA@mail.gmail.com>
On Tue, May 24, 2011 at 00:01, Linus Torvalds wrote:
> On Mon, May 23, 2011 at 7:06 PM, Mike Frysinger wrote:
>>
>> more failures:
>
> Is this blackfin or something?
let's go with "something" ...
> I did an allyesconfig with a special x86 patch that should have caught
> everything that didn't have the proper prefetch.h include, but non-x86
> drivers would have passed that.
the isp1362-hcd failure probably is before your
268bb0ce3e87872cb9290c322b0d35bce230d88f. i think i was reading a log
that is a few days old (ive been traveling and am playing catch up
atm). i'll refresh and see what's what still.
the common musb code only allows it to be built if the arch glue is
available, and there is no x86 glue. so an allyesconfig on x86
wouldnt have picked up the failure. it'll bomb though for any target
which does have the glue.
-mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-05-24 4:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 6:18 linux-next: build failure after merge of the final tree Stephen Rothwell
2011-05-24 2:06 ` Mike Frysinger
2011-05-24 2:51 ` Greg KH
2011-05-24 3:59 ` Stephen Rothwell
2011-05-24 12:48 ` Greg KH
2011-05-24 21:52 ` Stephen Rothwell
2011-05-24 4:01 ` Linus Torvalds
2011-05-24 4:10 ` Mike Frysinger [this message]
2011-05-24 17:10 ` Mike Frysinger
2011-05-24 17:29 ` Linus Torvalds
2011-05-25 9:24 ` Felipe Balbi
2011-05-25 12:13 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 6:23 Stephen Rothwell
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=BANLkTim-zRShhy49d7yn5WTJYzR6A2DtZQ@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).