From: "Gustavo F. Padovan" <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
To: Vitaly Wool <vitalywool-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig
Date: Sun, 27 Feb 2011 16:19:01 -0300 [thread overview]
Message-ID: <20110227191901.GC2166@joana> (raw)
In-Reply-To: <AANLkTimuyx4ixPq5BexRHozebVpjry2k-2xskqVf79g1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Vitaly,
* Vitaly Wool <vitalywool-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> [2011-02-26 18:52:44 +0100]:
> Hi Gustavo,
>
> On Sat, Feb 26, 2011 at 2:41 AM, Gustavo F. Padovan
> <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org> wrote:
> > If we want something "bool" built-in in something "tristate" it can't
> > "depend on" the tristate config option.
> >
> > Report by DaveM:
> >
> > I give it 'y' just to make it happen, for both, and afterways no
> > matter how many times I rerun "make oldconfig" I keep seeing things
> > like this in my build:
> >
> > scripts/kconfig/conf --silentoldconfig Kconfig
> > include/config/auto.conf:986:warning: symbol value 'm' invalid for BT_SCO
> > include/config/auto.conf:3156:warning: symbol value 'm' invalid for BT_L2CAP
> >
> > Reported-by: David S. Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
> > Signed-off-by: Gustavo F. Padovan <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
> > ---
> > net/bluetooth/Kconfig | 6 ++++--
> > 1 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
> > index c6f9c2f..6ae5ec5 100644
> > --- a/net/bluetooth/Kconfig
> > +++ b/net/bluetooth/Kconfig
> > @@ -31,9 +31,10 @@ menuconfig BT
> > to Bluetooth kernel modules are provided in the BlueZ packages. For
> > more information, see <http://www.bluez.org/>.
> >
> > +if BT != n
> > +
> > config BT_L2CAP
> > bool "L2CAP protocol support"
> > - depends on BT
> > select CRC16
> > help
> > L2CAP (Logical Link Control and Adaptation Protocol) provides
> > @@ -42,11 +43,12 @@ config BT_L2CAP
> >
> > config BT_SCO
> > bool "SCO links support"
> > - depends on BT
> > help
> > SCO link provides voice transport over Bluetooth. SCO support is
> > required for voice applications like Headset and Audio.
> >
> > +endif
> > +
>
> Ugh, isn't it far cleaner to change initial dependencies to "depends
> on BT != n" ?
I just followed the same approach as net/ipv6/Kconfig and
net/mac80211/Kconfig.
Dave, how do you prefer this?
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-02-27 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:52 pull request: wireless-next-2.6 2011-02-22 John W. Linville
[not found] ` <20110222215229.GJ12153-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2011-02-25 6:43 ` David Miller
[not found] ` <20110224.224344.104068328.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-02-25 19:15 ` David Miller
[not found] ` <20110225.111500.59674472.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-02-25 19:36 ` Gustavo F. Padovan
2011-02-26 1:36 ` Gustavo F. Padovan
2011-02-26 1:41 ` [PATCH] Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig Gustavo F. Padovan
2011-02-26 17:52 ` Vitaly Wool
[not found] ` <AANLkTimuyx4ixPq5BexRHozebVpjry2k-2xskqVf79g1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-27 19:19 ` Gustavo F. Padovan [this message]
[not found] ` <1298684485-3081-1-git-send-email-padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
2011-03-03 5:54 ` David Miller
[not found] ` <20110302.215433.39198854.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-03-03 14:05 ` John W. Linville
2011-02-25 19:48 ` pull request: wireless-next-2.6 2011-02-22 John W. Linville
2011-03-04 4:35 ` Shan Wei
[not found] ` <4D706C2E.40307-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2011-03-04 18:40 ` 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=20110227191901.GC2166@joana \
--to=padovan-y3zbgmpkuga34eueqzhozw@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vitalywool-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).