From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, cpufeature: Suppress compiler warning with gcc 3.x
Date: Thu, 03 Jun 2010 09:11:51 +0200 [thread overview]
Message-ID: <4C0755B7.8030304@linux.intel.com> (raw)
In-Reply-To: <201006030452.o534qPZa022225@www262.sakura.ne.jp>
On 06/03/2010 06:52 AM, Tetsuo Handa wrote:
> Gcc 3.x generates a warning
>
> arch/x86/include/asm/cpufeature.h: In function `__static_cpu_has':
> arch/x86/include/asm/cpufeature.h:315: warning: asm operand 1 probably doesn't match constraints
>
> on each file.
> But static_cpu_has() for gcc 3.x does not need __static_cpu_has().
>
> Signed-off-by: Tetsuo Handa<penguin-kernel@I-love.SAKURA.ne.jp>
Patch already queued for this.
Why are you trying to compile a current kernel with gcc 3.x?
-hpa
prev parent reply other threads:[~2010-06-03 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 4:52 [PATCH] x86, cpufeature: Suppress compiler warning with gcc 3.x Tetsuo Handa
2010-06-03 7:11 ` H. Peter Anvin [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=4C0755B7.8030304@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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