From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sbcinfo.c frame_len problem?
Date: Tue, 15 Mar 2005 08:57:48 -0700 [thread overview]
Message-ID: <423705FC.7010908@xmission.com> (raw)
In-Reply-To: <1110873260.8820.8.camel@pegasus>
Marcel
> actually the answer to this was easier then I thought. The bug is not in
> line 195. I don't even had to read the specification to find the answer
> to this problem. The display of the value is simply wrong.
thanks! Sorry I didn't catch that. I closed the bug.
Brad
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-15 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 7:01 [Bluez-devel] sbcinfo.c frame_len problem? Brad Midgley
2005-03-15 7:44 ` Marcel Holtmann
2005-03-15 7:54 ` Marcel Holtmann
2005-03-15 15:57 ` Brad Midgley [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=423705FC.7010908@xmission.com \
--to=bmidgley@xmission.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 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.