From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <JBeulich@novell.com>, Tejun Heo <tj@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fix percpu_{to,from}_op()
Date: Mon, 11 May 2009 21:20:09 +0200 [thread overview]
Message-ID: <20090511192009.GE28684@elte.hu> (raw)
In-Reply-To: <4A08652802000078000004F8@vpn.id2.novell.com>
* Jan Beulich <JBeulich@novell.com> wrote:
> - the byte operand constraints were wrong for 32-bit
> - the to-op's input operands weren't properly parenthesized
>
> [ Impact: compilation problem fix ]
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> ---
> arch/x86/include/asm/percpu.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
applied to x86/urgent, thanks.
Btw., what kind of compilation problem did you experience? Did GCC
bail out with a constraint error (which version?), or did you get a
miscompiled kernel?
Ingo
prev parent reply other threads:[~2009-05-11 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 15:49 Jan Beulich
2009-05-11 19:20 ` Ingo Molnar [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=20090511192009.GE28684@elte.hu \
--to=mingo@elte.hu \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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®