From: Marcel Holtmann <marcel@holtmann.org>
To: Frank Maas <frank.maas@cheiron-it.nl>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Problem with 'inquiry_cache' in sysfs
Date: Fri, 05 Feb 2010 11:50:09 -0800 [thread overview]
Message-ID: <1265399409.31341.241.camel@localhost.localdomain> (raw)
In-Reply-To: <20100204220516.GC8556@xs4all.nl>
Hi Frank,
> I have just connected to your mailing list as this is your prefered way
> of contact. So excuse me for barging in a bit... And excuse me if the
> following is too much text...
>
> I am currently developing a system that relies heavily on the Linux
> bluetooth stack. That system uses the sysfs interface to the kernel
> module and more specifically the entry 'inquiry_cache' of the device
> "directory".
that file should have been moved to debugfs, but we haven't done that
yet. It really doesn't belong in sysfs at all. And should not be treated
as an API.
Regards
Marcel
next prev parent reply other threads:[~2010-02-05 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 22:05 Problem with 'inquiry_cache' in sysfs Frank Maas
2010-02-05 19:50 ` Marcel Holtmann [this message]
2010-02-07 13:30 ` Frank Maas
2010-02-08 7:48 ` Luiz Augusto von Dentz
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=1265399409.31341.241.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=frank.maas@cheiron-it.nl \
--cc=linux-bluetooth@vger.kernel.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).