From: mirko_3 <mirko_3@gmx.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Headset connected, respondig, but silent
Date: Wed, 19 Jan 2005 22:20:40 +0100 [thread overview]
Message-ID: <20050119222040.6c3ede44@mirko_3> (raw)
In-Reply-To: <41EE9921.9050807@dark-reality.de>
Tried again, with the patch, but nothing changed, same dmesg as before...
--
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-19 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050118195131.CD122EACF@sc8-sf-spam2.sourceforge.net>
2005-01-19 15:15 ` [Bluez-devel] Headset connected, respondig, but silent mirko_3
2005-01-19 17:30 ` Lars Grunewaldt
2005-01-19 21:20 ` mirko_3 [this message]
2005-01-19 22:10 ` [Bluez-devel] " Paul Ionescu
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=20050119222040.6c3ede44@mirko_3 \
--to=mirko_3@gmx.net \
--cc=bluez-devel@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