From: Guillaume Bedot <littletux@zarb.org>
To: Louis JANG <louis@mizi.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [Bluez-devel] forcing SCO connection patch
Date: Thu, 28 Feb 2008 11:57:04 +0100 [thread overview]
Message-ID: <1204196224.9466.15.camel@littletux> (raw)
In-Reply-To: <47C62147.90007@mizi.com>
On jeu, 2008-02-28 at 11:49 +0900, Louis JANG wrote:
> Hi Marcel,
>
> I changed what you said below and attached patch again.
>
> And did you check Guillaume's patch for this issue? his patch try to
> find again when ev->link_type is SCO_LINK only. I think his way is
> better than mine. I haven't saw other case (LM is not support esco but
> ESCO_LINK is connected) and I think it shouldn't happen in a normal
> situation.
Perhaps my patch fixes half of the issue, as it does not get a handle on
the other case, and I just miss the point.
The cases represented in the "Messages Sequences Chart" are said to be
"examples", and they cover all the possible cases.
Maybe I just lack imagination.
If I have no example, it doesn't matter : if it happens, the same issue
will occur if the two link types aren't tried.
Best regards,
Guillaume B.
prev parent reply other threads:[~2008-02-28 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 12:39 [Bluez-devel] forcing SCO connection patch Louis JANG
2008-02-25 6:43 ` Brad Midgley
2008-02-25 6:56 ` Brad Midgley
2008-02-26 19:19 ` Guillaume Bedot
2008-02-26 19:28 ` Marcel Holtmann
2008-02-26 21:05 ` Guillaume Bedot
[not found] ` <a8e1da0802242330l765b8b1ava62b857baf8a5568@mail.gmail.com>
[not found] ` <47C28A33.4070102@mizi.com>
[not found] ` <a8e1da0802250155u1b7af481va203849f68d9106b@mail.gmail.com>
[not found] ` <47C2A7FA.2060902@mizi.com>
[not found] ` <70692DDF-93B7-447E-ABEE-3CDBD94F15F1@holtmann.org>
[not found] ` <47C38D40.3040809@mizi.com>
[not found] ` <B96BD3FE-F490-4AD5-9315-ECD42CE9C728@holtmann.org>
[not found] ` <47C4C3D4.8010902@mizi.com>
[not found] ` <2A7EF87C-1340-45D7-B457-F81799674B1E@holtmann.org>
[not found] ` <47C555E5.2000903@mizi.com>
2008-02-27 13:04 ` Guillaume Bedot
[not found] ` <5D9353FF-6A69-4039-9033-C0EBD1CDA756@holtmann.org>
[not found] ` <47C62147.90007@mizi.com>
2008-02-28 10:57 ` Guillaume Bedot [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=1204196224.9466.15.camel@littletux \
--to=littletux@zarb.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=louis@mizi.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