From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: "Ozan Çağlayan" <ozancag@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Hauke Mehrtens <hauke@hauke-m.de>, <backports@vger.kernel.org>,
<mcgrof@kernel.org>
Subject: Re: [PATCH] compat-drivers: Add possibility to build every subsystem separately
Date: Tue, 12 Mar 2013 13:36:38 -0700 [thread overview]
Message-ID: <20130312203638.GJ32416@pogo> (raw)
In-Reply-To: <CAFub=KRfAsohiy3U9gAsjY=nfsPCreTboYhiZ=NcJqp+x07=5w@mail.gmail.com>
On Tue, Mar 12, 2013 at 02:12:15PM +0200, Ozan Çağlayan wrote:
> > I read this thread when I got back from the mountains and agreed with
> > Hauke's recommendation.
> >
> > Luis
>
> Can you clarify what does $BT, BT=True achieve? It looks like it was
> some kind of switch to enable/disable BT but I can't be sure.
Yeah that's legacy junk, nuke it at your liking.
> On the other part, Hauke first suggested a different thing and then another
> way.
I think the concern was to not build everything on the stock
vanilla release.
> Should we enable all by default and --disable the unwanted ones or
> should we disable and print a usage by default and add --enable
> switches to enable subsystems?
How about something very simple:
* Enable all by default
* Use Kconfig to allow us to select 4 subsystems:
- Ethernet
- WiFi
- Bluetooth
- DRM
This way we'd keep the logic easy for an initial implementation
to support Kconfig (scripts/kconfig/mconf.c) and then build on
top of it to expand specifics.
Luis
next prev parent reply other threads:[~2013-03-12 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 18:33 [PATCH] compat-drivers: Add possibility to build every subsystem separately Ozan Çağlayan
2013-02-03 19:10 ` Hauke Mehrtens
2013-02-03 19:19 ` Ozan Çağlayan
2013-02-12 21:18 ` Hauke Mehrtens
2013-03-12 9:13 ` Ozan Çağlayan
2013-03-12 10:51 ` Luis R. Rodriguez
2013-03-12 12:12 ` Ozan Çağlayan
2013-03-12 20:36 ` Luis R. Rodriguez [this message]
2013-03-15 8:48 ` Luis R. Rodriguez
2013-03-15 9:09 ` Ozan Çağlayan
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=20130312203638.GJ32416@pogo \
--to=rodrigue@qca.qualcomm.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@kernel.org \
--cc=ozancag@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