linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
@ 2010-10-19  8:45 Bala Shanmugam
  2010-10-19  8:53 ` Luis R. Rodriguez
  0 siblings, 1 reply; 5+ messages in thread
From: Bala Shanmugam @ 2010-10-19  8:45 UTC (permalink / raw)
  To: lrodriguez, mcgrof; +Cc: linux-wireless, Bala Shanmugam

---
 Makefile |    9 ++++-----
 1 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/Makefile b/Makefile
index bca92ca..ec84197 100644
--- a/Makefile
+++ b/Makefile
@@ -31,17 +31,16 @@ obj-$(CONFIG_COMPAT_NET_USB_MODULES) += drivers/net/usb/
 
 obj-$(CONFIG_COMPAT_NETWORK_MODULES) += drivers/net/
 obj-$(CONFIG_COMPAT_VAR_MODULES) +=  drivers/ssb/ drivers/misc/eeprom/
-endif
-
-obj-$(CONFIG_COMPAT_BLUETOOTH) += net/bluetooth/
-obj-$(CONFIG_COMPAT_BLUETOOTH_MODULES) += drivers/bluetooth/
-
 
 ifeq ($(CONFIG_STAGING_EXCLUDE_BUILD),)
 obj-$(CONFIG_COMPAT_STAGING) += drivers/staging/ath6kl/
 obj-$(CONFIG_COMPAT_STAGING) += drivers/staging/brcm80211/
 endif
 
+endif
+
+obj-$(CONFIG_COMPAT_BLUETOOTH) += net/bluetooth/
+obj-$(CONFIG_COMPAT_BLUETOOTH_MODULES) += drivers/bluetooth/
 
 else
 
-- 
1.6.3.3


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
  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
  0 siblings, 2 replies; 5+ messages in thread
From: Luis R. Rodriguez @ 2010-10-19  8:53 UTC (permalink / raw)
  To: Bala Shanmugam; +Cc: linux-wireless

Applied, you may want a ./scripts/driver-select entry as well.

  Luis

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
  2010-10-19  8:53 ` Luis R. Rodriguez
@ 2010-10-19  9:07   ` Bala Shanmugam
  2010-10-19 13:35   ` Walter Goldens
  1 sibling, 0 replies; 5+ messages in thread
From: Bala Shanmugam @ 2010-10-19  9:07 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: Shanmugamkamatchi Balashanmugam, linux-wireless@vger.kernel.org

  On 10/19/2010 2:23 PM, Luis R. Rodriguez wrote:
> Applied, you may want a ./scripts/driver-select entry as well.
>
>    Luis
Not needed for now as we have seperate targets to compile, install and 
uninstall bluetooth modules.

Bala.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
  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
  1 sibling, 1 reply; 5+ messages in thread
From: Walter Goldens @ 2010-10-19 13:35 UTC (permalink / raw)
  To: Bala Shanmugam, Luis R. Rodriguez; +Cc: linux-wireless


> 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"

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 ;)

Walter.


      

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] Do not compile staging directory for bt target. Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
  2010-10-19 13:35   ` Walter Goldens
@ 2010-10-19 16:59     ` Luis R. Rodriguez
  0 siblings, 0 replies; 5+ messages in thread
From: Luis R. Rodriguez @ 2010-10-19 16:59 UTC (permalink / raw)
  To: Walter Goldens; +Cc: Bala Shanmugam, linux-wireless

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-10-19 16:59 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).