public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: linux-next: acpi tree build failure
Date: Fri, 06 Feb 2009 23:06:28 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0902062303090.26256@localhost.localdomain> (raw)
In-Reply-To: <20090205050056.GA7651@kroah.com>


On Wed, 4 Feb 2009, Greg KH wrote:

> On Thu, Feb 05, 2009 at 01:13:40PM +1100, Stephen Rothwell wrote:
> > Greg, Len,
> > 
> > On Mon, 2 Feb 2009 13:22:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > drivers/platform/x86/oqo-wmi.c: In function 'oqo_kine_init':
> > > drivers/platform/x86/oqo-wmi.c:595: error: 'struct device' has no member named 'bus_id'
> > > 
> > > Caused by commit 03919980ad590ad5c5c181d1bd7d58513ad170bc ("platform/x86:
> > > Add oqo-wmi driver for model 2 OQO backlight and rfkill control")
> > > interacting with commit c44c8304353aa6da82cbf98040c6a9c254e68e1c ("driver
> > > core: get rid of struct device's bus_id string array") from the
> > > driver-core tree.
> > 
> > Still getting this (of course).  Can you guys come up with a fix, please?
> 
> Len, you have the patch from Kay, what do you want to do with it?

I don't recall a patch from Kay specifically for OQO.
OQO is sitting in my tree to get exposure while it waits for
a few updates from Matthew.

I think it can be restored with this 1 liner, which I can apply to it.

thanks,
Len Brown, Intel Open Source Technology Center


diff --git a/drivers/platform/x86/oqo-wmi.c b/drivers/platform/x86/oqo-wmi.c
index 940e605..0a88af8 100644
--- a/drivers/platform/x86/oqo-wmi.c
+++ b/drivers/platform/x86/oqo-wmi.c
@@ -592,7 +592,7 @@ static int __devinit oqo_kine_init(void)
 	    oqo_kine->absmax[ABS_Y] =
 	    oqo_kine->absmax[ABS_Z] = oqo_kine->absmax[ABS_MISC] = 32767;
 
-	memcpy(oqo_kine->dev.bus_id, "kine", 4);
+	dev_set_name(&oqo_kine->dev, "kine");
 
 	oqo_kine_polled = input_allocate_polled_device();
 	if (!oqo_kine_polled) {

  reply	other threads:[~2009-02-07  5:07 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02  2:22 linux-next: acpi tree build failure Stephen Rothwell
2009-02-05  2:13 ` Stephen Rothwell
2009-02-05  5:00   ` Greg KH
2009-02-07  4:06     ` Len Brown [this message]
2009-02-07  5:32       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2009-12-14  1:20 Stephen Rothwell
2009-12-14 19:20 ` Bjorn Helgaas
2009-12-15  4:57 ` Bjorn Helgaas
2009-12-15 22:37   ` Len Brown
2009-12-15 23:28     ` Stephen Rothwell
2009-12-16  2:28     ` Stephen Rothwell
2009-09-26  2:15 Stephen Rothwell
2009-09-26  3:11 ` Bjorn Helgaas
2009-09-27  1:27   ` Crane Cai
2009-09-27  7:54     ` Len Brown
2009-09-01  2:57 Stephen Rothwell
2009-09-07 13:46 ` Stephen Rothwell
2009-09-08  0:47   ` Zhang Rui
2009-09-09  4:02     ` Len Brown
2009-09-09  5:45       ` Stephen Rothwell
2009-06-30  3:16 Stephen Rothwell
2009-07-06  6:18 ` Stephen Rothwell
2009-07-07  3:17 ` Len Brown
2009-07-07  3:53   ` Stephen Rothwell
2009-04-24  4:46 Stephen Rothwell
2009-04-24 15:15 ` Len Brown
2009-03-18  0:57 Stephen Rothwell
2009-03-18  1:09 ` Lin Ming
2009-03-18  3:27   ` Stephen Rothwell
2009-03-27 20:49     ` Len Brown
2009-02-24  4:37 Stephen Rothwell
2009-03-03  1:47 ` Stephen Rothwell
2009-03-16  5:10   ` Stephen Rothwell
2009-03-27 20:58   ` Len Brown
2008-10-15  5:08 Stephen Rothwell
2008-10-15  5:15 ` Shaohua Li
2008-10-15  4:51 Stephen Rothwell
2008-08-12  3:16 Stephen Rothwell
2008-08-12  7:06 ` Andi Kleen
2008-08-12 20:07   ` Carlos Corbacho
2008-08-12 21:29 ` Carlos Corbacho

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=alpine.LFD.2.00.0902062303090.26256@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --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