From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: x86 maintainers <x86@kernel.org>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
airlied@linux.ie, netdev@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [git-pull -tip V2] fix compilation warnings
Date: Wed, 11 Feb 2009 21:05:55 +0100 [thread overview]
Message-ID: <20090211200555.GA1636@elte.hu> (raw)
In-Reply-To: <1234379780.3910.8.camel@localhost.localdomain>
* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> The following changes since commit 5765fcf36081bafa06b9553376bd99ceb629beb8:
> Ingo Molnar (1):
> Merge branch 'linus'
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tipclean.git master
>
> Jaswinder Singh Rajput (7):
> x86: mm/init_32.c fix compilation warning
> x86: kernel/mpparse.c fix compilation warnings
> drm_proc.c fix compilation warning
> falcon fix compilation warnings
> iscsi_ibft.c fix compilation warning
> ne3210.c fix compilation warning for phys_addr_t
> arlan-main.c fix compilation warnings for phys_addr_t
>
> arch/x86/kernel/mpparse.c | 6 +++---
> arch/x86/mm/init_32.c | 2 +-
> drivers/firmware/iscsi_ibft.c | 4 ++--
> drivers/gpu/drm/drm_proc.c | 4 ++--
> drivers/net/ne3210.c | 3 ++-
> drivers/net/sfc/falcon.c | 24 ++++++++++++------------
> drivers/net/wireless/arlan-main.c | 4 ++--
> 7 files changed, 24 insertions(+), 23 deletions(-)
Pulled, thanks Jaswinder.
For those wondering about how these files can be affected by the x86 tree,
it's fallout of:
976e8f6: x86: asm/io.h: unify virt_to_phys/phys_to_virt
Which standardized the return type of virt_to_phys() to phys_addr_t, and
caused these build warnings.
Ingo
prev parent reply other threads:[~2009-02-11 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 18:43 [git-pull -tip] " Jaswinder Singh Rajput
2009-02-11 19:16 ` [git-pull -tip V2] " Jaswinder Singh Rajput
2009-02-11 20:05 ` 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=20090211200555.GA1636@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=jaswinder@kernel.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome