From: Bjorn Helgaas <helgaas@kernel.org>
To: Jingoo Han <jingoohan1@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: sparse warnings
Date: Wed, 30 Sep 2020 17:39:28 -0500 [thread overview]
Message-ID: <20200930223928.GA2643255@bjorn-Precision-5520> (raw)
In-Reply-To: <20200729194815.GA1961117@bjorn-Precision-5520>
On Wed, Jul 29, 2020 at 02:48:15PM -0500, Bjorn Helgaas wrote:
> Just FYI, I see the following sparse warnings (among others):
>
> $ make C=2 drivers/pci/
>
> drivers/pci/endpoint/functions/pci-epf-test.c:288:24: warning: incorrect type in argument 1 (different address spaces)
> drivers/pci/endpoint/functions/pci-epf-test.c:288:24: expected void *to
> drivers/pci/endpoint/functions/pci-epf-test.c:288:24: got void [noderef] <asn:2> *[assigned] dst_addr
> drivers/pci/endpoint/functions/pci-epf-test.c:288:34: warning: incorrect type in argument 2 (different address spaces)
> drivers/pci/endpoint/functions/pci-epf-test.c:288:34: expected void const *from
> drivers/pci/endpoint/functions/pci-epf-test.c:288:34: got void [noderef] <asn:2> *[assigned] src_addr
>
> drivers/pci/controller/dwc/pcie-designware.c:447:52: warning: cast truncates bits from constant value (ffffffff7fffffff becomes 7fffffff)
>
> It'd be nice to fix these if it's practical.
Any ideas about these?
Bjorn
next prev parent reply other threads:[~2020-09-30 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 19:48 sparse warnings Bjorn Helgaas
2020-09-30 22:39 ` Bjorn Helgaas [this message]
2020-10-01 6:29 ` Kishon Vijay Abraham I
-- strict thread matches above, loose matches on Subject: below --
2020-08-04 21:36 Michael S. Tsirkin
2008-10-28 15:57 Johannes Berg
2008-10-29 8:06 ` Holger Schurig
2008-09-11 10:46 Johannes Berg
2008-06-27 19:52 Sparse warnings Larry Finger
2008-06-27 19:53 ` Pavel Roskin
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=20200930223928.GA2643255@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.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.