From: Johan Hedberg <johan.hedberg@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Send management event for class of device changes
Date: Wed, 22 Feb 2012 19:56:45 +0200 [thread overview]
Message-ID: <20120222175645.GA28313@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1329932281-15409-1-git-send-email-marcel@holtmann.org>
Hi Marcel,
On Wed, Feb 22, 2012, Marcel Holtmann wrote:
> Currently there are no events to other management sockets if the class of
> device got changed. So make sure they are sent.
>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
> include/net/bluetooth/hci_core.h | 1 +
> net/bluetooth/hci_event.c | 13 +++++++++----
> net/bluetooth/mgmt.c | 9 +++++++++
> 3 files changed, 19 insertions(+), 4 deletions(-)
Applied (after fixing a couple of 82-character lines). Thanks.
Johan
prev parent reply other threads:[~2012-02-22 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:38 [PATCH] Bluetooth: Send management event for class of device changes Marcel Holtmann
2012-02-22 17:56 ` 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=20120222175645.GA28313@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).