From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Daryl Van Vorst <daryl@wideray.com>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] RE: Rfcomm qualification
Date: 11 Aug 2003 21:03:14 +0200 [thread overview]
Message-ID: <1060628601.7752.93.camel@pegasus> (raw)
In-Reply-To: <000c01c36027$bfdfc490$1a01010a@baked>
Hi Daryl,
> Have you two worked out a solution for this one (see message below)?
I am working on another way to solve this problem. The patch in
2.4.18-mh8 should work, but it is not the best solution.
> Should I use the last patch you sent to test?
Give it a try, because it should pass the test.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-08-11 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 20:58 Rfcomm qualification Daryl Van Vorst
2003-07-29 23:03 ` [Bluez-devel] " Marcel Holtmann
2003-07-30 16:25 ` Daryl Van Vorst
2003-07-30 17:22 ` [Bluez-devel] " Marcel Holtmann
2003-07-30 21:43 ` Marcel Holtmann
2003-07-31 0:01 ` Max Krasnyansky
2003-07-31 0:48 ` Marcel Holtmann
2003-08-05 17:10 ` Max Krasnyansky
2003-08-05 22:04 ` Marcel Holtmann
2003-08-11 16:43 ` Daryl Van Vorst
2003-08-11 19:03 ` Marcel Holtmann [this message]
2003-08-14 17:39 ` Daryl Van Vorst
2003-08-14 17:48 ` Marcel Holtmann
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=1060628601.7752.93.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
--cc=maxk@qualcomm.com \
/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