From: Sylvain Munaut <tnt@246tNt•com>
To: Linux PPC Dev <linuxppc-dev@ozlabs•org>
Subject: [PATCH] Add __iomem qualifier to cfg_{addr,data} fields in stuct pci_controller
Date: Thu, 16 Dec 2004 15:17:41 +0100 [thread overview]
Message-ID: <41C19905.6070300@246tNt.com> (raw)
Hello,
The patch below add the __iomem qualifier to the fields containing
addresses to access the PCI config space. It seems right to add them
since they're gonna be used with {in,out}_{le,be} that requires them
not to produce sparse warning.
Sylvain
ppc32: Add __iomem qualifier to cfg_{addr,data} fields in stuct
pci_controller
Signed-off-by: Sylvain Munaut <tnt@246tNt•com>
===== include/asm-ppc/pci-bridge.h 1.13 vs edited =====
--- 1.13/include/asm-ppc/pci-bridge.h 2004-11-11 09:25:52 +01:00
+++ edited/include/asm-ppc/pci-bridge.h 2004-12-16 15:07:14 +01:00
@@ -57,8 +57,8 @@
unsigned long pci_mem_offset;
struct pci_ops *ops;
- volatile unsigned int *cfg_addr;
- volatile unsigned char *cfg_data;
+ volatile unsigned int __iomem *cfg_addr;
+ volatile unsigned char __iomem *cfg_data;
/*
* If set, indirect method will set the cfg_type bit as
* needed to generate type 1 configuration transactions.
reply other threads:[~2004-12-16 14:17 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=41C19905.6070300@246tNt.com \
--to=tnt@246tnt$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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