From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bart Westgeest <bart@elbrys.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Feedback on potential fix for issue while advertising Feature List
Date: Sat, 10 Nov 2012 14:25:35 +0200 [thread overview]
Message-ID: <20121110122535.GA26532@x220.P-661HNU-F1> (raw)
In-Reply-To: <509D879C.1080205@elbrys.com>
Hi Bart,
On Fri, Nov 09, 2012, Bart Westgeest wrote:
> > I appreciate any input from anybody more familiar with the SDP
> > code on what the accepted/preferred approach is to get this
> > issue fixed.
>
> Anybody? Again, I've already root caused the problem and have a fix.
>
> I am Just looking for input to see if what I have is acceptable, or
> if something else is preferred.
Have a bit more patience, sometimes it can take a few days to get
feedback. I think the option of looking at the length and using the old
type for < 256 and a 16-bit type for greater lengths would be the
safest. This way old code will still produce the same result for < 256
lengths.
Johan
next prev parent reply other threads:[~2012-11-10 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 15:34 Feedback on potential fix for issue while advertising Feature List Bart Westgeest
2012-11-09 22:45 ` Bart Westgeest
2012-11-10 12:25 ` Johan Hedberg [this message]
2012-11-12 19:36 ` Bart Westgeest
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=20121110122535.GA26532@x220.P-661HNU-F1 \
--to=johan.hedberg@gmail.com \
--cc=bart@elbrys.com \
--cc=linux-bluetooth@vger.kernel.org \
/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