From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Where are BlueZ located in Linux kernel
Date: Tue, 16 Aug 2005 17:29:51 +0200 [thread overview]
Message-ID: <1124206191.7466.9.camel@pegasus> (raw)
In-Reply-To: <E64BAD5A8AD46740828069A678D9DD73011A84@netbe01.net.unimis>
Hi Al,
> As fas as I know, the following bluetooh directories are where BlueZ
> located:
>
> 1. linux/drivers/bluetooth (for bluetooth device driver)
> 2. linux/net/bluetooth (for bluetooth protocol stack)
> 3. linux/include/net/bluetooth (for bluetooth include file)
>
> Is there any other I miss ?
no, that's all.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-08-16 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 10:19 [Bluez-users] Where are BlueZ located in Linux kernel Al
2005-08-16 15:29 ` Marcel Holtmann [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=1124206191.7466.9.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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