public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] undefined reference to `kobject_actions'
Date: Sun, 29 Jul 2007 14:01:07 -0700	[thread overview]
Message-ID: <20070729210107.GA22492@kroah.com> (raw)
In-Reply-To: <20070729204110.GB18225@flint.arm.linux.org.uk>

On Sun, Jul 29, 2007 at 09:41:10PM +0100, Russell King wrote:
> On Sun, Jul 29, 2007 at 09:59:05PM +0200, Kay Sievers wrote:
> > 
> > On Sun, 2007-07-29 at 20:37 +0100, Russell King wrote:
> > > On Sun, Jul 29, 2007 at 08:34:01PM +0100, Russell King wrote:
> > > > Many ARM platforms fail to build with the following:
> > > > 
> > > > drivers/built-in.o: In function `store_uevent':
> > > > hid-input.c:(.text+0x19c4c): undefined reference to `kobject_actions'
> > > > 
> > > > It appears that if hotplug is disabled, kobject_actions is ifdef'd
> > > > away but hid-input still references it.
> > > 
> > > What I also meant to say is that it looks like it's caused by
> > > commit 60a96a59569bab85571d0089682109bd3324e896.
> > > 
> > > Presumably if hotplug is disabled, we want store_uevent to be
> > > removed as well?
> > 
> > Does this patch fix it?
> >   http://lkml.org/lkml/2007/7/20/143
> 
> Yup, thanks.  Any idea when this fix will hit mainline?  Looks like
> it's 9 days old, and it fixes real build errors.

I've been at OSCON all last week, this will go to Linus on Monday.
Sorry for the delay, conference season sucks at times...

thanks,

greg k-h

      reply	other threads:[~2007-07-29 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 19:34 [BUG] undefined reference to `kobject_actions' Russell King
2007-07-29 19:34 ` Gabriel C
2007-07-29 19:37 ` Russell King
2007-07-29 19:59   ` Kay Sievers
2007-07-29 20:41     ` Russell King
2007-07-29 21:01       ` Greg KH [this message]

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=20070729210107.GA22492@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.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