From: Jeff Garzik <jeff@garzik.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Wu Zhangjin <wuzhangjin@gmail.com>, Zhang Le <r0bertz@gentoo.org>,
Chen Jie <chenj@lemote.com>
Subject: Re: linux-next: build warning after merge of the Linus' tree
Date: Sun, 26 Dec 2010 19:49:13 -0500 [thread overview]
Message-ID: <4D17E289.2040505@garzik.org> (raw)
In-Reply-To: <20101227095812.0f727881.sfr@canb.auug.org.au>
On 12/26/2010 05:58 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
>
> drivers/ata/pata_cs5536.c:47:1: warning: "rdmsr" redefined
> In file included from arch/x86/include/asm/irqflags.h:60,
> from include/linux/irqflags.h:15,
> from arch/x86/include/asm/system.h:11,
> from arch/x86/include/asm/processor.h:17,
> from include/linux/prefetch.h:14,
> from include/linux/list.h:7,
> from include/linux/module.h:9,
> from drivers/ata/pata_cs5536.c:33:
> arch/x86/include/asm/paravirt.h:146:1: warning: this is the location of the previous definition
> drivers/ata/pata_cs5536.c:48:1: warning: "wrmsr" redefined
> arch/x86/include/asm/paravirt.h:154:1: warning: this is the location of the previous definition
>
> Caused by commit 9272dcc232b84ccb027d6861077934055d42764d ("pata_cs5536:
> Add support for non-X86_32 platforms").
Just sent a fix upstream.
The fix is a bit ugly ("#undef rdmsr" etc.), but that driver does not
need anything more extensive.
next prev parent reply other threads:[~2010-12-27 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 22:58 linux-next: build warning after merge of the Linus' tree Stephen Rothwell
2010-12-27 0:49 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-21 2:17 Stephen Rothwell
2011-11-21 8:25 ` Guennadi Liakhovetski
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=4D17E289.2040505@garzik.org \
--to=jeff@garzik.org \
--cc=chenj@lemote.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=r0bertz@gentoo.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=wuzhangjin@gmail.com \
/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