LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for January 18 (__modver_version_show)
Date: Wed, 19 Jan 2011 17:12:54 -0800	[thread overview]
Message-ID: <20110120011254.GA14742@core.coreip.homeip.net> (raw)
In-Reply-To: <4D37890A.5000005@oracle.com>

On Wed, Jan 19, 2011 at 04:59:54PM -0800, Randy Dunlap wrote:
> On 01/19/11 16:38, Dmitry Torokhov wrote:
> > On Wed, Jan 19, 2011 at 08:12:19AM -0800, Randy Dunlap wrote:
> >> On 01/19/11 08:10, Randy Dunlap wrote:
> >>> On 01/18/11 21:09, Stephen Rothwell wrote:
> >>>> Hi Randy,
> >>>>
> >>>> On Tue, 18 Jan 2011 09:17:49 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> >>>>>
> >>>>> I'm seeing this on several builds (i386 and x86_64):
> >>>>>
> >>>>> lib/built-in.o:(__modver+0x8): undefined reference to `__modver_version_show'
> >>>>> lib/built-in.o:(__modver+0x2c): undefined reference to `__modver_version_show'
> >>>>>
> >>>>> It looks like the compiler or linker is dropping that function from the
> >>>>> build since it cannot see any references to it...
> >>>>> At least __modver_version_show is not in the kernel/params.o file.
> >>>>
> >>>> Do these builds have CONFIG_SYSFS set?
> >>>>
> >>>
> >>> Yes, they all do (50 random builds have CONFIG_SYSFS=y).
> >>
> >> Gawd, what bad grepping this morning.
> >>
> >> You hit the nail.  They do not have SYSFS enabled.
> >>
> > 
> > Argh, this one is my fault, the following should fix it.
> > 
> 
> Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
> 

Great!

Hopefully Rusty will be able to fold it in the original change so it
won't break bisects.

-- 
Dmitry

      reply	other threads:[~2011-01-20  1:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  1:21 linux-next: Tree for January 18 Stephen Rothwell
2011-01-18 17:17 ` linux-next: Tree for January 18 (__modver_version_show) Randy Dunlap
2011-01-19  5:09   ` Stephen Rothwell
2011-01-19 16:10     ` Randy Dunlap
2011-01-19 16:12       ` Randy Dunlap
2011-01-19 22:18         ` Rusty Russell
2011-01-20  0:38         ` Dmitry Torokhov
2011-01-20  0:59           ` Randy Dunlap
2011-01-20  1:12             ` Dmitry Torokhov [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=20110120011254.GA14742@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rusty@rustcorp.com.au \
    --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).