From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Roel Kluin <roel.kluin@gmail.com>
Subject: Re: linux-next: driver-core tree build failure
Date: Tue, 12 May 2009 17:13:17 -0700 [thread overview]
Message-ID: <20090513001317.GA15527@kroah.com> (raw)
In-Reply-To: <20090512040518.GA2407@kroah.com>
On Mon, May 11, 2009 at 09:05:18PM -0700, Greg KH wrote:
> On Tue, May 12, 2009 at 01:44:01PM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > Today's linux-next build (powerpc_ppc64_defconfig) failed like this:
> >
> > In file included from arch/powerpc/platforms/ps3/platform.h:28,
> > from arch/powerpc/platforms/ps3/mm.c:32:
> > arch/powerpc/include/asm/ps3.h: In function 'ps3_system_bus_set_driver_data':
> > arch/powerpc/include/asm/ps3.h:424: error: 'struct device' has no member named 'driver_data'
> > arch/powerpc/include/asm/ps3.h: In function 'ps3_system_bus_get_driver_data':
> > arch/powerpc/include/asm/ps3.h:429: error: 'struct device' has no member named 'driver_data'
> >
> > Caused (obviously) by commit 9499952d8efc857406365bfc04079ff1e85660ff
> > ("Driver core: move dev_get/set_drvdata to drivers/base/dd.c") which I
> > have reverted.
> >
> > Grep is your friend ...
>
> Do you know how many false-positives there currently are for hitting
> driver_data? It's insane... I got 'make allmodconfig' working for
> i386, x86-64, and s390, and I thought ps3 as well, sorry about that.
>
> > Actually there is a patch for this ...
> > http://patchwork.ozlabs.org/patch/27061/ ... also for another ...
> > http://patchwork.ozlabs.org/patch/27062/
> >
> > Please leave the above commit out of the tree until you have at least
> > fixed all the in tree users.
I've now dropped the offending patch and will work to fix up the rest of
these before adding it back.
thanks,
greg k-h
next prev parent reply other threads:[~2009-05-13 0:16 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 3:44 linux-next: driver-core tree build failure Stephen Rothwell
2009-05-12 4:05 ` Greg KH
2009-05-13 0:13 ` Greg KH [this message]
2009-05-13 1:39 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-07-14 6:33 Stephen Rothwell
2009-07-14 7:31 ` David Brownell
2009-07-16 22:50 ` Greg KH
2009-06-23 6:01 Stephen Rothwell
2009-06-23 15:29 ` Greg KH
2009-06-23 16:28 ` Greg KH
2009-05-04 6:25 Stephen Rothwell
2009-05-04 13:00 ` Kay Sievers
2009-05-05 4:18 ` Stephen Rothwell
2009-05-05 4:29 ` Greg KH
2009-05-09 11:16 ` Stephen Rothwell
2009-05-09 13:51 ` Greg KH
2009-03-26 7:34 Stephen Rothwell
2009-03-26 23:00 ` Jesse Barnes
2009-03-16 9:47 Stephen Rothwell
2009-03-22 12:22 ` Stephen Rothwell
2009-03-23 4:23 ` David Miller
2009-03-10 8:24 Stephen Rothwell
2009-03-10 13:31 ` Geert Uytterhoeven
2009-03-10 13:38 ` Herbert Xu
2009-03-10 13:53 ` Martin Schwidefsky
2009-03-10 15:29 ` Geert Uytterhoeven
2009-03-10 16:08 ` Martin Schwidefsky
2009-03-10 20:02 ` Jason Baron
2009-03-11 3:30 ` Greg KH
2009-03-11 8:33 ` Geert Uytterhoeven
2009-03-11 10:07 ` Greg Banks
2009-03-11 10:50 ` Geert Uytterhoeven
2009-03-11 15:12 ` Jason Baron
2009-01-26 0:50 Stephen Rothwell
2009-01-26 1:10 ` Greg KH
2009-01-26 12:19 ` Kay Sievers
2009-01-26 17:40 ` Greg KH
2008-12-22 12:59 Stephen Rothwell
2008-12-22 14:50 ` Mark McLoughlin
2008-12-23 4:29 ` Greg KH
2008-12-29 6:34 ` Stephen Rothwell
2008-12-30 15:28 ` Stephen Rothwell
2009-01-02 7:26 ` Greg KH
2009-01-03 4:32 ` Stephen Rothwell
2008-12-11 0:21 Stephen Rothwell
2008-12-11 4:55 ` Greg KH
2008-11-19 0:30 Stephen Rothwell
2008-11-19 0:40 ` Kay Sievers
2008-11-19 2:22 ` Stephen Rothwell
2008-11-19 2:24 ` Stephen Rothwell
2008-11-19 6:36 ` Greg KH
2008-11-19 5:43 ` Stephen Rothwell
2008-11-19 6:26 ` Greg KH
2008-11-19 6:51 ` Stephen Rothwell
2008-11-19 6:55 ` Greg KH
2008-09-12 3:53 Stephen Rothwell
2008-09-15 18:58 ` Greg KH
2008-08-15 8:25 Stephen Rothwell
2008-08-16 5:31 ` Greg KH
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=20090513001317.GA15527@kroah.com \
--to=greg@kroah.com \
--cc=linux-next@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).