From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
Julia Lawall <julia@diku.dk>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 pci acpi: fix type mismatch
Date: Wed, 1 Jun 2011 11:51:15 -0700 [thread overview]
Message-ID: <20110601115115.214427ca@jbarnes-desktop> (raw)
In-Reply-To: <4DCEBB85.8040709@freemail.hu>
On Sat, 14 May 2011 19:27:33 +0200
Németh Márton <nm127@freemail.hu> wrote:
> From: Márton Németh <nm127@freemail.hu>
>
> The flags field of struct resource from linux/ioport.h is "unsigned long". Change
> the "type" parameter of coalesce_windows() function to match that field. This fixes
> the following warning messages when compiling with "make C=1 W=1 bzImage modules":
>
> arch/x86/pci/acpi.c: In function ‘coalesce_windows’:
> arch/x86/pci/acpi.c:198: warning: conversion to ‘long unsigned int’ from ‘int’ may change the sign of the result
> arch/x86/pci/acpi.c:203: warning: conversion to ‘long unsigned int’ from ‘int’ may change the sign of the result
>
> Signed-off-by: Márton Németh <nm127@freemail.hu>
> ---
> --- linux-2.6.39-rc6/arch/x86/pci/acpi.c.orig 2011-05-04 04:59:13.000000000 +0200
> +++ linux-2.6.39-rc6/arch/x86/pci/acpi.c 2011-05-14 19:12:42.000000000 +0200
> @@ -188,7 +188,7 @@ static bool resource_contains(struct res
> return false;
> }
>
> -static void coalesce_windows(struct pci_root_info *info, int type)
> +static void coalesce_windows(struct pci_root_info *info, unsigned long type)
> {
> int i, j;
> struct resource *res1, *res2;
Applied to my for-linus tree, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2011-06-01 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 17:27 [PATCH] x86 pci acpi: fix type mismatch Németh Márton
2011-06-01 18:51 ` Jesse Barnes [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=20110601115115.214427ca@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=hpa@zytor.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nm127@freemail.hu \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.