From: Imre Deak <imre.deak@nokia.com>
To: Bluez-Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Work on L2CAP retransmission and flow control support
Date: Tue, 15 Mar 2005 17:04:51 +0200 [thread overview]
Message-ID: <1110899091.11567.12.camel@mammoth.research.nokia.com> (raw)
In-Reply-To: <1110898225.9818.2.camel@pegasus>
Hi,
Yes I'm dealing with RFC. It's more or less ready, I'm still doing some
SMP bugfixing..
Could you tell me what are the parts that are affected?
--Imre
On Tue, 2005-03-15 at 15:50 +0100, ext Marcel Holtmann wrote:
> Hi,
>
> I have some plans to reorder and cleanup a lot of the L2CAP code. This
> might be bad for anyone who is working on the L2CAP RFC support. So if
> there is anyone, please drop me a note.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-15 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 14:50 [Bluez-devel] Work on L2CAP retransmission and flow control support Marcel Holtmann
2005-03-15 15:04 ` Imre Deak [this message]
2005-03-15 16:08 ` 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=1110899091.11567.12.camel@mammoth.research.nokia.com \
--to=imre.deak@nokia.com \
--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