From: Thierry Reding <thierry.reding@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Bjorn Helgaas' <bhelgaas@google.com>,
linux-pci@vger.kernel.org, 'Stephen Warren' <swarren@nvidia.com>
Subject: Re: [PATCH 1/3] PCI: tegra: add missing __iomem annotation
Date: Thu, 19 Sep 2013 13:28:49 +0200 [thread overview]
Message-ID: <20130919112848.GD10852@ulmo> (raw)
In-Reply-To: <000201ceaf9b$098780b0$1c968210$%han@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Thu, Sep 12, 2013 at 06:32:45PM +0900, Jingoo Han wrote:
> Added missing __iomem annotation in order to fix the following
> sparse warnings:
>
> drivers/pci/host/pci-tegra.c:411:41: warning: incorrect type in return expression (different address spaces)
> drivers/pci/host/pci-tegra.c:411:41: expected void [noderef] <asn:2>*
> drivers/pci/host/pci-tegra.c:411:41: got void *addr
> drivers/pci/host/pci-tegra.c:419:25: warning: incorrect type in return expression (different address spaces)
> drivers/pci/host/pci-tegra.c:419:25: expected void [noderef] <asn:2>*
> drivers/pci/host/pci-tegra.c:419:25: got void *addr
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/pci/host/pci-tegra.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I can carry this in a local tree or if somebody else wants to take it:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-09-19 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 9:32 [PATCH 1/3] PCI: tegra: add missing __iomem annotation Jingoo Han
2013-09-12 9:36 ` [PATCH 2/3] PCI: mvebu: make local functions static Jingoo Han
2013-09-12 9:37 ` Thomas Petazzoni
2013-09-12 9:37 ` [PATCH 3/3] PCI: mvebu: add missing __iomem annotation Jingoo Han
2013-09-16 15:57 ` Thomas Petazzoni
2013-09-17 0:52 ` Jingoo Han
2013-09-17 4:47 ` Thomas Petazzoni
2013-09-19 11:28 ` Thierry Reding [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=20130919112848.GD10852@ulmo \
--to=thierry.reding@gmail.com \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=linux-pci@vger.kernel.org \
--cc=swarren@nvidia.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;
as well as URLs for NNTP newsgroup(s).