From: Bjorn Helgaas <helgaas@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the pci tree
Date: Mon, 20 Jun 2016 14:11:36 -0500 [thread overview]
Message-ID: <20160620191136.GA17036@localhost> (raw)
In-Reply-To: <20160620115213.07231836@canb.auug.org.au>
On Mon, Jun 20, 2016 at 11:52:13AM +1000, Stephen Rothwell wrote:
> Hi Bjorn,
>
> After merging the pci tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
>
> drivers/pci/host/pci-host-common.c: In function 'gen_pci_init':
> drivers/pci/host/pci-host-common.c:88:10: warning: return makes pointer from integer without a cast [-Wint-conversion]
> return err;
> ^
> drivers/pci/host/pci-host-common.c:93:10: warning: return makes pointer from integer without a cast [-Wint-conversion]
> return PTR_ERR(cfg);
> ^
> drivers/pci/host/pci-host-common.c:108:9: warning: return makes pointer from integer without a cast [-Wint-conversion]
> return err;
> ^
>
> Introduced by commit
>
> 3f8dcfc3fbba ("PCI: generic: Free resource list close to where it's allocated")
Fixed, thanks a lot, Stephen!
next prev parent reply other threads:[~2016-06-20 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 1:52 linux-next: build warnings after merge of the pci tree Stephen Rothwell
2016-06-20 19:11 ` Bjorn Helgaas [this message]
2016-06-21 1:08 ` Stephen Rothwell
2016-06-21 1:27 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 5:09 Stephen Rothwell
2024-02-06 20:21 ` Philipp Stanner
2022-03-01 2:59 Stephen Rothwell
2022-03-01 15:01 ` Bjorn Helgaas
2018-10-02 0:26 Stephen Rothwell
2018-10-02 13:47 ` Bjorn Helgaas
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612CE1@blrx3m08.blr.amer.dell.com>
2010-08-02 12:44 ` Narendra K
2010-08-02 1:18 Stephen Rothwell
2010-08-02 1:38 ` Stephen Rothwell
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=20160620191136.GA17036@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).