From: John W. Linville <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH] b43: add default option to avoid duplicating device support with brcmsmac
Date: Fri, 13 Jan 2012 14:20:01 -0500 [thread overview]
Message-ID: <20120113192000.GD18899@tuxdriver.com> (raw)
In-Reply-To: <20120113013248.30123.qmail@stuge.se>
On Fri, Jan 13, 2012 at 02:32:48AM +0100, Peter Stuge wrote:
> John W. Linville wrote:
> > The summary line could be different as well, if you can think of a
> > better way to describe the issue. I am open to suggestions.
>
> I think these terms are clear:
>
> Community b43 driver
> Broadcom brcmsmac driver
>
> How to apply them I leave up to you. :)
Maybe you think that is clear, but it doesn't do much for me.
I could say "Support for devices already supported by the
Broadcom-supported brcmsmac driver"?
John
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: [PATCH] b43: add default option to avoid duplicating device support with brcmsmac
Date: Fri, 13 Jan 2012 14:20:01 -0500 [thread overview]
Message-ID: <20120113192000.GD18899@tuxdriver.com> (raw)
In-Reply-To: <20120113013248.30123.qmail@stuge.se>
On Fri, Jan 13, 2012 at 02:32:48AM +0100, Peter Stuge wrote:
> John W. Linville wrote:
> > The summary line could be different as well, if you can think of a
> > better way to describe the issue. I am open to suggestions.
>
> I think these terms are clear:
>
> Community b43 driver
> Broadcom brcmsmac driver
>
> How to apply them I leave up to you. :)
Maybe you think that is clear, but it doesn't do much for me.
I could say "Support for devices already supported by the
Broadcom-supported brcmsmac driver"?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-01-13 19:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 20:53 [PATCH] b43: add default option to avoid duplicating device support with brcmsmac John W. Linville
2012-01-11 21:03 ` Arend van Spriel
2012-01-11 21:07 ` John W. Linville
2012-01-12 16:11 ` Rafał Miłecki
2012-01-12 16:11 ` Rafał Miłecki
2012-01-12 16:17 ` John W. Linville
2012-01-12 16:17 ` John W. Linville
2012-01-13 1:32 ` Peter Stuge
2012-01-13 1:32 ` Peter Stuge
2012-01-13 19:20 ` John W. Linville [this message]
2012-01-13 19:20 ` John W. Linville
2012-01-13 2:07 ` Julian Calaby
2012-01-13 19:20 ` John W. Linville
2012-01-13 19:20 ` John W. Linville
2012-01-13 21:52 ` Julian Calaby
2012-01-16 20:22 ` [PATCH v2] " John W. Linville
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=20120113192000.GD18899@tuxdriver.com \
--to=linville@tuxdriver.com \
--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 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.