From: Avi Kivity <avi@redhat.com>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, riel@redhat.com, gleb@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm: Fix section mismatch derived from kvm_guest_cpu_online()
Date: Wed, 02 Feb 2011 11:10:44 +0200 [thread overview]
Message-ID: <4D491F94.6070803@redhat.com> (raw)
In-Reply-To: <AANLkTi=V6PvG42bBmE=7qcm=5vvk=SeUJ6a8oMKOcihb@mail.gmail.com>
On 02/02/2011 09:55 AM, Sedat Dilek wrote:
> On Tue, Jan 4, 2011 at 10:03 PM, Marcelo Tosatti<mtosatti@redhat.com> wrote:
> > On Mon, Jan 03, 2011 at 12:01:29AM +0100, Sedat Dilek wrote:
> >> > From my build.log:
> >>
> >> WARNING: arch/x86/built-in.o(.text+0x1bb74): Section mismatch in reference from the function kvm_guest_cpu_online() to the function .cpuinit.text:kvm_guest_cpu_init()
> >> The function kvm_guest_cpu_online() references
> >> the function __cpuinit kvm_guest_cpu_init().
> >> This is often because kvm_guest_cpu_online lacks a __cpuinit
> >> annotation or the annotation of kvm_guest_cpu_init is wrong.
> >>
> >> This patch fixes the warning.
> >>
> >> Tested with linux-next (next-20101231)
> >>
> >> Signed-off-by: Sedat Dilek<sedat.dilek@gmail.com>
> >
> > Applied, thanks.
> >
> >
>
> PING!
>
> Was this patch really applied? I have it still in my patch-series.
>
It was applied to kvm.git and will find its way upstream eventually.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-02 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 23:01 [PATCH] kvm: Fix section mismatch derived from kvm_guest_cpu_online() Sedat Dilek
2011-01-02 23:39 ` Rik van Riel
2011-01-03 21:36 ` H. Peter Anvin
2011-01-04 9:48 ` Avi Kivity
2011-01-04 21:03 ` Marcelo Tosatti
2011-02-02 7:55 ` Sedat Dilek
2011-02-02 9:10 ` Avi Kivity [this message]
2011-02-02 9:25 ` Sedat Dilek
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=4D491F94.6070803@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
--cc=tglx@linutronix.de \
--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.