All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	x86 maintainers <x86@kernel.org>, Greg KH <gregkh@suse.de>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: linux-next: Tree for Nov 9 (build errors summary)
Date: Wed, 09 Nov 2011 12:55:24 -0800	[thread overview]
Message-ID: <4EBAE8BC.3040902@xenotime.net> (raw)
In-Reply-To: <20111109201136.GA5760@phenom.dumpdata.com>

On 11/09/2011 12:11 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Nov 09, 2011 at 11:23:21AM -0800, Randy Dunlap wrote:
>> On 11/08/2011 06:58 PM, Stephen Rothwell wrote:
>>> Hi all,
>>
>>
>> 1.  on i386, when CONFIG_SMP is not enabled:
>>
>> arch/x86/built-in.o: In function `hpet_setup_msi_irq':
>> hpet.c:(.text+0x12114): undefined reference to `arch_setup_hpet_msi'
>> hpet.c:(.text+0x12123): undefined reference to `destroy_irq'
>> arch/x86/built-in.o: In function `hpet_msi_capability_lookup':
>> hpet.c:(.text+0x121fb): undefined reference to `create_irq_nr'
>> arch/x86/built-in.o:(.data+0x314): undefined reference to `native_setup_msi_irqs'
>> arch/x86/built-in.o:(.data+0x318): undefined reference to `native_teardown_msi_irq'
> 
> This looks new. When did it start happening? err, Any idea which patch
> might have caused this?

I first reported it on the Nov. 7 linux-next tree.

No idea what patch might be causing it, sorry.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2011-11-09 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09  2:58 linux-next: Tree for Nov 9 Stephen Rothwell
2011-11-09 19:23 ` linux-next: Tree for Nov 9 (build errors summary) Randy Dunlap
2011-11-09 20:11   ` Konrad Rzeszutek Wilk
2011-11-09 20:55     ` Randy Dunlap [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=4EBAE8BC.3040902@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.