From: Joerg Roedel <joerg.roedel@amd.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [iommu:ioapic-cleanups 17/19] arch/x86/built-in.o:(.data+0x288): undefined reference to `native_
Date: Wed, 08 Aug 2012 10:44:12 +0000 [thread overview]
Message-ID: <20120808104412.GR1996@amd.com> (raw)
In-Reply-To: <20120807192751.GA5762@localhost>
Hi Fengguang,
On Wed, Aug 08, 2012 at 03:27:51AM +0800, Fengguang Wu wrote:
> FYI, kernel build failed on
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git ioapic-cleanups
> head: 25b140f9d56483def20a4a6cd54766a55508c132
> commit: 3f3c5417231f180b2f0fba968caa91979cb6e3f0 [17/19] x86, msi: Introduce x86_msi.compose_msi_msg call-back
> config: i386-randconfig-b732 (attached as .config)
>
> All related error/warning messages:
>
> arch/x86/built-in.o:(.data+0x288): undefined reference to `native_compose_msi_msg'
>
> i386-randconfig-b731 all accumulated errors:
>
> arch/x86/kernel/x86_init.c:118:21: error: 'native_compose_msi_msg' undeclared here (not in a function)
> arch/x86/kernel/x86_init.c:130:14: error: 'native_disable_io_apic' undeclared here (not in a function)
> arch/x86/kernel/x86_init.c:131:20: error: 'native_io_apic_print_entries' undeclared here (not in a function)
> arch/x86/kernel/x86_init.c:133:18: error: 'native_setup_ioapic_entry' undeclared here (not in a function)
> arch/x86/kernel/x86_init.c:134:21: error: 'native_setup_timer_pin' undeclared here (not in a function)
Thanks a lot for your build-testing :) I fixed the issues you sent me and
found a couple more of them which I fixed too.
Thanks again,
Joerg
next prev parent reply other threads:[~2012-08-08 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 19:27 [iommu:ioapic-cleanups 17/19] arch/x86/built-in.o:(.data+0x288): undefined reference to `native_comp Fengguang Wu
2012-08-08 10:44 ` Joerg Roedel [this message]
2012-08-08 10:53 ` [iommu:ioapic-cleanups 17/19] arch/x86/built-in.o:(.data+0x288): undefined reference to `native_ Fengguang Wu
2012-08-08 12:29 ` Joerg Roedel
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=20120808104412.GR1996@amd.com \
--to=joerg.roedel@amd.com \
--cc=kernel-janitors@vger.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.