From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: padovan@profusion.mobi, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig
Date: Thu, 3 Mar 2011 09:05:12 -0500 [thread overview]
Message-ID: <20110303140512.GB8969@tuxdriver.com> (raw)
In-Reply-To: <20110302.215433.39198854.davem@davemloft.net>
On Wed, Mar 02, 2011 at 09:54:33PM -0800, David Miller wrote:
> From: "Gustavo F. Padovan" <padovan@profusion.mobi>
> Date: Fri, 25 Feb 2011 22:41:25 -0300
>
> > 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@davemloft.net>
> > Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
>
> I think this approach is fine since it mirrors what we use in other similar
> situations.
>
> I am assuming this patch will propagate via bluetooth --> wireless --> me.
Yes, I have it queued.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: padovan-Y3ZbgMPKUGA34EUeqzHoZw@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: Thu, 3 Mar 2011 09:05:12 -0500 [thread overview]
Message-ID: <20110303140512.GB8969@tuxdriver.com> (raw)
In-Reply-To: <20110302.215433.39198854.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Wed, Mar 02, 2011 at 09:54:33PM -0800, David Miller wrote:
> From: "Gustavo F. Padovan" <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
> Date: Fri, 25 Feb 2011 22:41:25 -0300
>
> > 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>
>
> I think this approach is fine since it mirrors what we use in other similar
> situations.
>
> I am assuming this patch will propagate via bluetooth --> wireless --> me.
Yes, I have it queued.
--
John W. Linville Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org might be all we have. Be ready.
next prev parent reply other threads:[~2011-03-03 14:05 UTC|newest]
Thread overview: 23+ 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
2011-02-25 6:43 ` David Miller
2011-02-25 6:43 ` David Miller
2011-02-25 19:15 ` David Miller
2011-02-25 19:15 ` David Miller
2011-02-25 19:36 ` Gustavo F. Padovan
2011-02-25 19:36 ` Gustavo F. Padovan
2011-02-26 1: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 1:41 ` Gustavo F. Padovan
2011-02-26 17:52 ` Vitaly Wool
2011-02-27 19:19 ` Gustavo F. Padovan
2011-02-27 19:19 ` Gustavo F. Padovan
2011-03-03 5:54 ` David Miller
2011-03-03 5:54 ` David Miller
2011-03-03 14:05 ` John W. Linville [this message]
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
2011-03-04 4:35 ` Shan Wei
2011-03-04 18:40 ` John W. Linville
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=20110303140512.GB8969@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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.