From: Fabien Chevalier <fabchevalier@free.fr>
To: Brad Midgley <bmidgley@xmission.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Updated SCO flow control patch: 2.6.23
Date: Wed, 10 Oct 2007 18:58:47 +0200 [thread overview]
Message-ID: <470D04C7.8040707@free.fr> (raw)
Brad & All,
I've tested the sco-flowcontrol-v4.3.diff patch.
It works perfectly fine when applied on 2.6.23-rc9, i guess 2.6.23 will
work too. :-)
As for sco-flowcontrol-v4.4.diff, which is against 2.6.22-mh3, i didn't
manage to test it due to broken sco behaviour. :-(
Cheers,
Fabien
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-10-10 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 16:58 Fabien Chevalier [this message]
2007-10-10 17:00 ` [Bluez-devel] Updated SCO flow control patch: 2.6.23 Brad Midgley
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=470D04C7.8040707@free.fr \
--to=fabchevalier@free.fr \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.