From: Bart Westgeest <bart@elbrys.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Feedback on potential fix for issue while advertising Feature List
Date: Fri, 09 Nov 2012 17:45:48 -0500 [thread overview]
Message-ID: <509D879C.1080205@elbrys.com> (raw)
In-Reply-To: <509BD103.2040808@elbrys.com>
> 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.
next prev parent reply other threads:[~2012-11-09 22:45 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 [this message]
2012-11-10 12:25 ` Johan Hedberg
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=509D879C.1080205@elbrys.com \
--to=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 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.