From: Johan Hedberg <johan.hedberg@gmail.com>
To: Alex Deymo <deymo@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, keybuk@chromium.org,
vinicius.gomes@openbossa.org
Subject: Re: [PATCH] core: Don't update a known long name with a short name.
Date: Wed, 8 May 2013 10:22:29 +0300 [thread overview]
Message-ID: <20130508072229.GC9401@x220> (raw)
In-Reply-To: <1367897517-12309-1-git-send-email-deymo@chromium.org>
Hi Alex,
On Mon, May 06, 2013, Alex Deymo wrote:
> update_found_devices() could attempt to update a device with new information
> containing only a short verstion of the name. If the struct eir_data passed
> has a short or NULL name, it will never update a previous name and will
> also trigger a "HCI Command: Remote Name Request" if the previous name was
> unknown.
> ---
> src/adapter.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2013-05-08 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 3:31 [PATCH] core: Don't update a known long name with a short name Alex Deymo
2013-05-08 7:22 ` Johan Hedberg [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=20130508072229.GC9401@x220 \
--to=johan.hedberg@gmail.com \
--cc=deymo@chromium.org \
--cc=keybuk@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.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