From: "Michael Büsch" <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: ChipCommon as independent driver?
Date: Fri, 01 Apr 2011 18:00:46 +0200 [thread overview]
Message-ID: <1301673646.5219.18.camel@maggie> (raw)
In-Reply-To: <AANLkTikGp+ZFhTtsaW7E4SO_5trte1_eF4KLWbkwVty5@mail.gmail.com> (sfid-20110401_104947_004628_8A7D9C8C)
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.
--
Greetings Michael.
next prev parent reply other threads:[~2011-04-01 16:00 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 [this message]
2011-04-01 16:06 ` Rafał Miłecki
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=1301673646.5219.18.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--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 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).