From: Bjorn Helgaas <helgaas@kernel.org>
To: Pratyush Anand <pratyush.anand@gmail.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, linux-pci@vger.kernel.org
Subject: pcie-spear13xx.c sparse warnings
Date: Wed, 30 Sep 2020 17:44:11 -0500 [thread overview]
Message-ID: <20200930224411.GA2643351@bjorn-Precision-5520> (raw)
FYI, sparse complains quite about about pcie-spear13xx.c:
$ make C=2 drivers/pci/controller/dwc/pcie-spear13xx.o
CHECK drivers/pci/controller/dwc/pcie-spear13xx.c
drivers/pci/controller/dwc/pcie-spear13xx.c:73:54: warning: incorrect type in initializer (different address spaces)
drivers/pci/controller/dwc/pcie-spear13xx.c:73:54: expected struct pcie_app_reg *app_reg
drivers/pci/controller/dwc/pcie-spear13xx.c:73:54: got void [noderef] __iomem *app_base
drivers/pci/controller/dwc/pcie-spear13xx.c:100:26: warning: incorrect type in argument 2 (different address spaces)
drivers/pci/controller/dwc/pcie-spear13xx.c:100:26: expected void volatile [noderef] __iomem *addr
drivers/pci/controller/dwc/pcie-spear13xx.c:100:26: got unsigned int *
...
Any ideas about how to fix these? I haven't looked into them at all.
I'm building on x86 with CONFIG_COMPILE_TEST=y and CONFIG_OF not set,
so probably not the typical config for this driver.
Bjorn
reply other threads:[~2020-09-30 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200930224411.GA2643351@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pratyush.anand@gmail.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