From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Walter Goldens <goldenstranger@yahoo.com>
Cc: Bala Shanmugam <sbalashanmugam@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
Date: Tue, 19 Oct 2010 09:59:06 -0700 [thread overview]
Message-ID: <AANLkTimp7fdHWm370A7Bq+XmCcLzMu9mo8wyB5urxe2O@mail.gmail.com> (raw)
In-Reply-To: <782419.6815.qm@web56803.mail.re3.yahoo.com>
On Tue, Oct 19, 2010 at 6:35 AM, Walter Goldens
<goldenstranger@yahoo.com> wrote:
>
>> Applied, you may want a
>
>>
>> Luis
> I was just about to submit exactly the same patch :)
>
> BTW, I was thinking, perhaps we could merge bt and ethernet drivers in one line, by two separate groups via driver-select. For example:
> Replace current:
> "Supported Ethernet drivers: < atl1 atl2 atl1e atl1c >"
> with
> "Supported Ethernet & Bluetooth drivers: < bt | eth (atlxx) >
>
> or something like that. This will notify users they can actually install bt drivers /if they don't read documentation/.
>
> Its a little weird that, atlxx are provided via driver-select and bt from 'make bt'. I believe they should be "on the same page"
Agreed.
> I would also suggest we drop the load.sh and wlload.sh scripts. I can't think of a reason why a sane person would opt for such iffy, redundant and probably malignant way to load their respective driver.
>
> There was something else, but I can't remember now ;)
Agreed.
Luis
prev parent reply other threads:[~2010-10-19 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 8:45 [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com> Bala Shanmugam
2010-10-19 8:53 ` Luis R. Rodriguez
2010-10-19 9:07 ` Bala Shanmugam
2010-10-19 13:35 ` Walter Goldens
2010-10-19 16:59 ` Luis R. Rodriguez [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=AANLkTimp7fdHWm370A7Bq+XmCcLzMu9mo8wyB5urxe2O@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=goldenstranger@yahoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sbalashanmugam@atheros.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).