b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Cc: b43-dev@lists.infradead.org, "Michael Buesch" <mb@bu3sch.de>,
	"Rafał Miłecki" <zajec5@gmail.com>
Subject: [RFC][PATCH] b43: use condition for SSB specific ops
Date: Thu, 2 Jun 2011 14:40:41 +0200	[thread overview]
Message-ID: <BANLkTim-ouepU2D7au3yH3dCt3S15cTamA@mail.gmail.com> (raw)
In-Reply-To: <1307013080-10386-1-git-send-email-zajec5@gmail.com>

W dniu 2 czerwca 2011 13:11 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
>
> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
> ---
> Abstracting bus by b43_bus_dev works fine, but there are few places
> where we calls SSB functions in uniq way. That calls happen only once
> in the whole code and so there is not much sense in putting them in
> bus abstraction.
>
> In this situation I have decided to use simple switches. It does not
> make code look lovely, but I do not have any better idea. If anyone
> have - comments are really welcome.

This final code would need to be something like:

switch (dev->dev->bus_type) {
#ifdef CONFIG_B43_BCMA
case B43_BUS_BCMA:
	dma->translation = bcma_dma_translation(dev->dev->bdev);
	break;
#endif
#ifdef CONFIG_B43_SSB
case B43_BUS_SSB:
	dma->translation = ssb_dma_translation(dev->dev->sdev);
	break;
#endif
}

So something nicer would be welcome. But what? :| Putting this in
bus.c? Even if that are once-callers?

-- 
Rafa?

      reply	other threads:[~2011-06-02 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 11:11 [RFC][PATCH] b43: use condition for SSB specific ops Rafał Miłecki
2011-06-02 12:40 ` Rafał Miłecki [this message]

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=BANLkTim-ouepU2D7au3yH3dCt3S15cTamA@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).