From: Randy Dunlap <randy.dunlap@oracle.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH v2] ssb: fix pcicore build breakage
Date: Fri, 13 May 2011 09:46:57 -0700 [thread overview]
Message-ID: <20110513094657.5d38e959.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1305296570-23671-1-git-send-email-linville@tuxdriver.com>
On Fri, 13 May 2011 10:22:50 -0400 John W. Linville wrote:
> drivers/ssb/main.c:1336: error: 'SSB_PCICORE_BCAST_ADDR' undeclared (first use in this function)
> drivers/ssb/main.c:1337: error: 'SSB_PCICORE_BCAST_DATA' undeclared (first use in this function)
> drivers/ssb/main.c:1349: error: 'struct ssb_pcicore' has no member named 'dev'
This patch does not fix the last error above when CONFIG_PCI is not enabled.
> Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> Use CHIPCO definitions since they should always(?) be valid...
>
> drivers/ssb/main.c | 10 ++++++----
> 1 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/ssb/main.c b/drivers/ssb/main.c
> index ee2937c..b2abd0f 100644
> --- a/drivers/ssb/main.c
> +++ b/drivers/ssb/main.c
> @@ -1332,14 +1332,16 @@ EXPORT_SYMBOL(ssb_bus_powerup);
> static void ssb_broadcast_value(struct ssb_device *dev,
> u32 address, u32 data)
> {
> +#ifdef CONFIG_SSB_DRIVER_PCICORE
> /* This is used for both, PCI and ChipCommon core, so be careful. */
> BUILD_BUG_ON(SSB_PCICORE_BCAST_ADDR != SSB_CHIPCO_BCAST_ADDR);
> BUILD_BUG_ON(SSB_PCICORE_BCAST_DATA != SSB_CHIPCO_BCAST_DATA);
> +#endif
>
> - ssb_write32(dev, SSB_PCICORE_BCAST_ADDR, address);
> - ssb_read32(dev, SSB_PCICORE_BCAST_ADDR); /* flush */
> - ssb_write32(dev, SSB_PCICORE_BCAST_DATA, data);
> - ssb_read32(dev, SSB_PCICORE_BCAST_DATA); /* flush */
> + ssb_write32(dev, SSB_CHIPCO_BCAST_ADDR, address);
> + ssb_read32(dev, SSB_CHIPCO_BCAST_ADDR); /* flush */
> + ssb_write32(dev, SSB_CHIPCO_BCAST_DATA, data);
> + ssb_read32(dev, SSB_CHIPCO_BCAST_DATA); /* flush */
> }
>
> void ssb_commit_settings(struct ssb_bus *bus)
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-05-13 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110512142303.8117a0b6.sfr@canb.auug.org.au>
2011-05-12 23:19 ` linux-next: Tree for May 12 (ssb) Randy Dunlap
2011-05-13 13:26 ` [PATCH] ssb: fix pcicore build breakage John W. Linville
2011-05-13 13:33 ` Rafał Miłecki
2011-05-13 13:33 ` John W. Linville
2011-05-13 14:14 ` Rafał Miłecki
2011-05-13 13:43 ` Michael Büsch
2011-05-13 13:48 ` Michael Büsch
2011-05-13 14:22 ` [PATCH v2] " John W. Linville
2011-05-13 16:46 ` Randy Dunlap [this message]
2011-05-13 19:07 ` [PATCH v3] " John W. Linville
2011-05-13 19:52 ` Rafał Miłecki
2011-05-13 20:01 ` Randy Dunlap
2011-05-13 13:31 ` linux-next: Tree for May 12 (ssb) Rafał Miłecki
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=20110513094657.5d38e959.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).