All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: "John W. Linville" <linville@tuxdriver.com>,
	"Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH] ssb: fix pcicore build breakage
Date: Fri, 13 May 2011 15:48:25 +0200	[thread overview]
Message-ID: <1305294505.12573.6.camel@maggie> (raw)
In-Reply-To: <1305294214.12573.3.camel@maggie>

On Fri, 2011-05-13 at 15:43 +0200, Michael Büsch wrote: 
> On Fri, 2011-05-13 at 09:26 -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'
> > 
> > Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> > Signed-off-by: John W. Linville <linville@tuxdriver.com>
> > ---
> >  drivers/ssb/main.c |    2 ++
> >  1 files changed, 2 insertions(+), 0 deletions(-)
> > 
> > diff --git a/drivers/ssb/main.c b/drivers/ssb/main.c
> > index ee2937c..a53fc4d 100644
> > --- a/drivers/ssb/main.c
> > +++ b/drivers/ssb/main.c
> > @@ -1332,6 +1332,7 @@ 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);
> > @@ -1340,6 +1341,7 @@ static void ssb_broadcast_value(struct ssb_device *dev,
> >  	ssb_read32(dev, SSB_PCICORE_BCAST_ADDR); /* flush */
> >  	ssb_write32(dev, SSB_PCICORE_BCAST_DATA, data);
> >  	ssb_read32(dev, SSB_PCICORE_BCAST_DATA); /* flush */
> > +#endif
> >  }
> >  
> >  void ssb_commit_settings(struct ssb_bus *bus)
> 
> This clearly is incorrect. Read the comment, please.

I think we should probably have two ssb_broadcast_value functions. One
for PCI core and one for chipcommon. That seems the best solution, even
if the constants happen to be the same. It's only a few lines of code.
(If the compiler is clever enough, it might probably be able to optimize
it out anyway).

-- 
Greetings Michael.


  reply	other threads:[~2011-05-13 13:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  4:23 linux-next: Tree for May 12 Stephen Rothwell
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 [this message]
2011-05-13 14:22       ` [PATCH v2] " John W. Linville
2011-05-13 16:46         ` Randy Dunlap
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=1305294505.12573.6.camel@maggie \
    --to=m@bues.ch \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=randy.dunlap@oracle.com \
    --cc=zajec5@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 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.