From: Ingo Molnar <mingo@elte.hu>
To: Avi Kivity <avi@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Tejun Heo <tj@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: percpu/kvm/tip tree build failure
Date: Mon, 2 Nov 2009 11:07:35 +0100 [thread overview]
Message-ID: <20091102100735.GB16963@elte.hu> (raw)
In-Reply-To: <4AEEAA82.8070705@redhat.com>
* Avi Kivity <avi@redhat.com> wrote:
> On 11/02/2009 07:17 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Today's linux-next build (x86_64 allmodconfig) failed like this:
>>
>> kernel/user-return-notifier.c: In function 'fire_user_return_notifiers':
>> kernel/user-return-notifier.c:45: error: expected expression before ')' token
>>
>> Introduced by commit 7c68af6e32c73992bad24107311f3433c89016e2 ("core,
>> x86: Add user return notifiers") from the tip and kvm trees but revealed
>> by commit e0fdb0e050eae331046385643618f12452aa7e73 ("percpu: add __percpu
>> for sparse") from the percpu tree. Before that percpu tree commit,
>> "put_cpu_var()" would compile without error (even though it really needs
>> a parameter).
>>
>> I have applied the following patch for today.
>>
>
> Ingo, can you queue this on x86/entry?
Already done, tested and pushed out.
Ingo
next prev parent reply other threads:[~2009-11-02 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 5:17 Stephen Rothwell
2009-11-02 9:46 ` Avi Kivity
2009-11-02 10:07 ` Ingo Molnar [this message]
2009-11-02 10:13 ` Avi Kivity
2009-11-02 10:28 ` Ingo Molnar
2009-11-02 10:13 ` [tip:x86/entry] x86: Fix user return notifier put_cpu_var() invocation tip-bot for Stephen Rothwell
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=20091102100735.GB16963@elte.hu \
--to=mingo@elte.hu \
--cc=avi@redhat.com \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®