From: alok barsode <alokbarsode@gmail.com>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: Re: Undefined symbols in netlink plugin
Date: Tue, 13 Oct 2009 15:53:05 +0530 [thread overview]
Message-ID: <8b5debfa0910130323t2a470e2alfef9c4ea79b0eeb5@mail.gmail.com> (raw)
In-Reply-To: <4AD430D0.3010109@pardus.org.tr>
Hi Ozan,
On Tue, Oct 13, 2009 at 1:18 PM, Ozan =C3=87a=C4=9Flayan <ozan@pardus.org.t=
r> wrote:
> alok barsode wrote On 12-10-2009 11:37:
>> The following patch fixes this issue but I am not sure if its the right =
way.
>> Let Marcel take a call on this.
>>
>>
> Yes that fixed it. BTW, is it normal to get messages like
>
> Failed to find Bluetooth netlink family
> Failed to init netlink plugin
>
At this point, yes. There in no netlink support in the kernel as of now.
> Does the netlink support really exist?
>
Not right now. But we are working on it.
Cheers,
Alok.
prev parent reply other threads:[~2009-10-13 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 22:22 Undefined symbols in netlink plugin Ozan Çağlayan
2009-10-12 6:48 ` Ozan Çağlayan
2009-10-12 8:37 ` alok barsode
2009-10-13 7:48 ` Ozan Çağlayan
2009-10-13 10:23 ` alok barsode [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=8b5debfa0910130323t2a470e2alfef9c4ea79b0eeb5@mail.gmail.com \
--to=alokbarsode@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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