From: Joe Perches <joe@perches.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Christopher Li' <sparse@chrisli.org>,
linux-sparse@vger.kernel.org,
'Dan Carpenter' <dan.carpenter@oracle.com>,
'Jason Gunthorpe' <jgunthorpe@obsidianresearch.com>,
'Jason Cooper' <jason@lakedaemon.net>,
'Thomas Petazzoni' <thomas.petazzoni@free-electrons.com>,
'Bjorn Helgaas' <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
'Ezequiel Garcia' <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
'Axel Lin' <axel.lin@ingics.com>,
'Julia Lawall' <julia.lawall@lip6.fr>
Subject: Re: PCI: mvebu: return NULL instead of ERR_PTR(ret)
Date: Tue, 26 Nov 2013 18:26:36 -0800 [thread overview]
Message-ID: <1385519196.18487.25.camel@joe-AO722> (raw)
In-Reply-To: <000101ceeb14$480fee80$d82fcb80$%han@samsung.com>
On Wed, 2013-11-27 at 10:59 +0900, Jingoo Han wrote:
[]
> ./drivers/pci/host/pci-mvebu.c
> static void __iomem *mvebu_pcie_map_registers(struct platform_device *pdev,
> struct device_node *np, struct mvebu_pcie_port *port)
> {
> .....
>
> ret = of_address_to_resource(np, 0, ®s);
> if (ret)
> - return ERR_PTR(ret);
> + return (void __iomem *)ERR_PTR(ret);
>
> However, other engineers said that "(void __iomem *)ERR_PTR(ret)"
> is not a general pattern. I cannot find the proper method to resolve
> this sparse warning.
>
> In this case, how can I resolve this sparse warning?
I think there's no problem using the cast. It's not a
pattern because it's not been required before as function
returns have not previously been declared __iomem.
Or, perhaps the arm|hexagon specific #define below could
be made generic so it could be used.
arch/arm/include/asm/io.h:#define IOMEM(x) ((void __force __iomem *)(x))
return IOMEM(ERR_PTR(ret));
There aren't any current uses of return IOMEM(foo) either
though so the direct cast is probably more appropriate.
next prev parent reply other threads:[~2013-11-27 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001001ceb816$5d1aecc0$1750c640$%han@samsung.com>
[not found] ` <20131125200256.GA7316@obsidianresearch.com>
[not found] ` <001101ceea68$cb486220$61d92660$%han@samsung.com>
[not found] ` <20131126180930.GC19852@obsidianresearch.com>
2013-11-27 1:59 ` PCI: mvebu: return NULL instead of ERR_PTR(ret) Jingoo Han
2013-11-27 2:17 ` [PATCH] linux/err.h: Provide an ERR_PTR_IO that returns an __iomem pointer Josh Triplett
2013-11-27 2:26 ` Joe Perches [this message]
2013-11-27 2:35 ` PCI: mvebu: return NULL instead of ERR_PTR(ret) Josh Triplett
2013-11-27 2:48 ` Joe Perches
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=1385519196.18487.25.camel@joe-AO722 \
--to=joe@perches.com \
--cc=axel.lin@ingics.com \
--cc=bhelgaas@google.com \
--cc=dan.carpenter@oracle.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jg1.han@samsung.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=thomas.petazzoni@free-electrons.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).