From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: Linux Wireless List <linux-wireless@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: CONFIG_BT_CMTP is not checked in compat-wireless
Date: Tue, 12 Jan 2010 15:51:11 -0800 [thread overview]
Message-ID: <43e72e891001121551n2caadccfy67db57ea0e3e97b0@mail.gmail.com> (raw)
In-Reply-To: <4B4CE9A0.3020902@pardus.org.tr>
On Tue, Jan 12, 2010 at 1:29 PM, Ozan Çağlayan <ozan@pardus.org.tr> wrote:
> Hi,
>
> CONFIG_BT_CMTP depends on BT && BT_L2CAP && ISDN_CAPI but in config.mk there isn't an explicit check for
> those conditions. On a ISDN_CAPI disabled kernel this causes unresolved symbols as cmtp.ko is built
>
> Something like below fixes the problem (at least for CMTP case) by not compiling net/bluetooth/cmtp:
>
> # CONFIG_BT_CMTP depends on ISDN_CAPI
> ifneq ($(CONFIG_BT_CMTP),)
> CONFIG_BT_CMTP=m
> endif
I applied this change, thanks for the report.
Luis
prev parent reply other threads:[~2010-01-12 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 21:29 CONFIG_BT_CMTP is not checked in compat-wireless Ozan Çağlayan
2010-01-12 23:51 ` 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=43e72e891001121551n2caadccfy67db57ea0e3e97b0@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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).