From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>, Greg KH <greg@kroah.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, avorontsov@ru.mvista.com
Subject: Re: next Feb 16 build break [usb/host/fhci-*]
Date: Mon, 16 Feb 2009 21:13:10 +1100 [thread overview]
Message-ID: <20090216211310.5513de1a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <499929CB.2030004@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Hi Sachin,
On Mon, 16 Feb 2009 14:24:35 +0530 "Sachin P. Sant" <sachinp@in.ibm.com> wrote:
>
> Feb 16 next tree randconfig build fails with
>
> drivers/usb/host/fhci-hcd.c: In function ‘of_fhci_probe’:
> drivers/usb/host/fhci-hcd.c:586: error: ‘struct device’ has no member named ‘bus_id’
> drivers/usb/host/fhci-hcd.c:653: error: ‘struct device’ has no member named ‘bus_id’
>
> drivers/usb/host/fhci-dbg.c: In function ‘fhci_dfs_create’:
> drivers/usb/host/fhci-dbg.c:111: error: ‘struct device’ has no member named ‘bus_id’
That would be the driver-core removing bus_id from struct device. cc's added.
fhci-hcd appeared between 2.6.29-rc2 and rc3.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-16 10:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 6:20 linux-next: Tree for February 16 Stephen Rothwell
2009-02-16 8:54 ` next Feb 16 build break [usb/host/fhci-*] Sachin P. Sant
2009-02-16 10:13 ` Stephen Rothwell [this message]
2009-02-16 13:40 ` [Patch - Next] [USB/FHCI] use dev_name() in place of bus_id Sachin P. Sant
2009-02-16 13:48 ` Anton Vorontsov
2009-02-16 16:46 ` [PATCH -next] staging/phison: fix kconfig for clean build Randy Dunlap
2009-02-17 0:55 ` next-20090216: slqb Alexey Dobriyan
2009-02-17 10:27 ` Nick Piggin
2009-02-17 11:31 ` Pekka Enberg
2009-02-17 12:48 ` Peter Zijlstra
2009-02-17 9:55 ` linux-next: USB mouse won't work after resume Laurent Riffard
2009-02-17 10:35 ` Oliver Neukum
2009-02-17 13:37 ` Laurent Riffard
2009-02-17 15:12 ` Alan Stern
2009-02-17 20:42 ` Oliver Neukum
2009-02-17 21:05 ` Alan Stern
2009-02-18 9:51 ` Jiri Slaby
2009-02-18 0:31 ` Laurent Riffard
2009-02-18 8:47 ` Oliver Neukum
2009-02-18 16:51 ` Alan Stern
2009-02-18 17:06 ` Oliver Neukum
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=20090216211310.5513de1a.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=avorontsov@ru.mvista.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sachinp@in.ibm.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
all inboxes | Powered by JetHome®