From: Greg KH <greg@kroah•com>
To: Mike Frysinger <vapier.adi@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linus <torvalds@linux-foundation•org>,
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: Mon, 23 May 2011 19:51:51 -0700 [thread overview]
Message-ID: <20110524025151.GA26939@kroah.com> (raw)
In-Reply-To: <BANLkTimjzzqTS1fELmpb0UivqseLsYOfPw@mail.gmail.com>
On Mon, May 23, 2011 at 10:06:40PM -0400, Mike Frysinger wrote:
> On Fri, May 20, 2011 at 02:18, Stephen Rothwell wrote:
> > Caused by commit e66eed651fd1 ("list: remove prefetching from regular list
> > iterators").
> >
> > I added the following patch for today:
>
> probably should get added to whatever tree that commit is coming from
> so we dont have bisect hell ?
>
> more failures:
> drivers/usb/host/isp1362-hcd.c: In function 'isp1362_write_ptd':
> drivers/usb/host/isp1362-hcd.c:355: error: implicit declaration of
> function 'prefetch'
> drivers/usb/host/isp1362-hcd.c: In function 'isp1362_read_ptd':
> drivers/usb/host/isp1362-hcd.c:377: error: implicit declaration of
> function 'prefetchw'
> make[3]: *** [drivers/usb/host/isp1362-hcd.o] Error 1
>
> drivers/usb/musb/musb_core.c: In function 'musb_write_fifo':
> drivers/usb/musb/musb_core.c:219: error: implicit declaration of
> function 'prefetch'
> make[3]: *** [drivers/usb/musb/musb_core.o] Error 1
>
> although it seems like it should be fairly trivial to look at the
> funcs in linux/prefetch.h, grep the tree, and find a pretty good list
> of the files that are missing the include
How did this not show up in linux-next? Where did the patch that caused
this show up from?
totally confused,
greg k-h
--
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 2:51 UTC|newest]
Thread overview: 24+ 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 [this message]
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
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-09-30 1:38 Stephen Rothwell
2011-09-30 2:49 ` Yoshihiro Shimoda
2010-05-25 4:10 Stephen Rothwell
2010-05-25 4:58 ` David Miller
2010-05-25 5:14 ` Herbert Xu
2010-05-25 6:56 ` David Miller
2010-04-08 5:35 Stephen Rothwell
2010-04-08 6:25 ` David Miller
2010-04-08 14:15 ` John Linn
2010-04-08 22:59 ` Stephen Rothwell
2010-04-08 23:01 ` John Linn
[not found] <20100318160220.b7eaded6.sfr@canb.auug.org.au>
2010-03-18 6:21 ` David Miller
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=20110524025151.GA26939@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dipankar@in$(echo .)ibm.com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mel@csn$(echo .)ul.ie \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=vapier.adi@gmail$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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