From: "Rolf Eike Beer" <eike-kernel@sf-tec.de>
To: "Yinghai Lu" <yinghai@kernel.org>
Cc: "Jesse Barnes" <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
"Yinghai Lu" <yinghai@kernel.org>
Subject: Re: [PATCH] PCI: Increase resource array mask bit size in pcim_iomap_regions()
Date: Thu, 5 Jan 2012 09:43:51 +0100 [thread overview]
Message-ID: <a2507aff2913b402cfb2d3e2a0bb887a.squirrel@webmail.sf-mail.de> (raw)
In-Reply-To: <1325721002-6094-1-git-send-email-yinghai@kernel.org>
> DEVICE_COUNT_RESOURCE will be bigger than 16 when SRIOV supported is
> enabled.
>
> Let them pass with int just like pci_enable_resources().
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> ---
> include/linux/pci.h | 6 +++---
> lib/devres.c | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> Index: linux-2.6/include/linux/pci.h
> ===================================================================
> --- linux-2.6.orig/include/linux/pci.h
> +++ linux-2.6/include/linux/pci.h
> @@ -1433,10 +1433,10 @@ static inline void pci_fixup_device(enum
> void __iomem *pcim_iomap(struct pci_dev *pdev, int bar, unsigned long
> maxlen);
> void pcim_iounmap(struct pci_dev *pdev, void __iomem *addr);
> void __iomem * const *pcim_iomap_table(struct pci_dev *pdev);
> -int pcim_iomap_regions(struct pci_dev *pdev, u16 mask, const char *name);
> -int pcim_iomap_regions_request_all(struct pci_dev *pdev, u16 mask,
> +int pcim_iomap_regions(struct pci_dev *pdev, int mask, const char *name);
> +int pcim_iomap_regions_request_all(struct pci_dev *pdev, int mask,
> const char *name);
[...]
You are switching from unsigned to signed here, is this intentional? In my
feeling such masks should end up in an unsigned int, no?
Eike
next prev parent reply other threads:[~2012-01-05 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 23:50 [PATCH] PCI: Increase resource array mask bit size in pcim_iomap_regions() Yinghai Lu
2012-01-05 8:43 ` Rolf Eike Beer [this message]
2012-01-05 17:10 ` Bjorn Helgaas
2012-01-05 18:50 ` Don Dutile
2012-01-06 21:05 ` Jesse Barnes
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=a2507aff2913b402cfb2d3e2a0bb887a.squirrel@webmail.sf-mail.de \
--to=eike-kernel@sf-tec.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).