From: "Rafał Miłecki" <zajec5@gmail.com>
To: "Michael Büsch" <mb@bu3sch.de>
Cc: b43-dev <b43-dev@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: ChipCommon as independent driver?
Date: Fri, 1 Apr 2011 18:06:16 +0200 [thread overview]
Message-ID: <BANLkTin2ZaBVbum9Y=iqWTwW4kzkdKAJnA@mail.gmail.com> (raw)
In-Reply-To: <1301673646.5219.18.camel@maggie>
W dniu 1 kwietnia 2011 18:00 u?ytkownik Michael B?sch <mb@bu3sch.de> napisa?:
> On Fri, 2011-04-01 at 16:49 +0200, Rafa? Mi?ecki wrote:
>> Do you have idea how we could nicely solve that issue?
>
> Yeah. Just don't share code between ssb and bcmai.
> That's the only clean solution to that mess.
Do you want to have core drivers separated as well? Really? Should we
have separated pci core? chiccommon core? gige core? 80211 (b43) core?
My mistake was to include ssb_private.h in separated chipcommon.
--
Rafa?
next prev parent reply other threads:[~2011-04-01 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 14:49 ChipCommon as independent driver? Rafał Miłecki
2011-04-01 16:00 ` Michael Büsch
2011-04-01 16:06 ` Rafał Miłecki [this message]
2011-04-01 16:15 ` Michael Büsch
2011-04-01 16:21 ` Rafał Miłecki
2011-04-01 16:30 ` Michael Büsch
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='BANLkTin2ZaBVbum9Y=iqWTwW4kzkdKAJnA@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--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).