linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: btusb: Use proper data structures for Intel vendor events
Date: Thu, 9 Apr 2015 10:42:38 +0300	[thread overview]
Message-ID: <20150409074238.GA27217@t440s.lan> (raw)
In-Reply-To: <1428564919-10398-1-git-send-email-marcel@holtmann.org>

Hi Marcel,

On Thu, Apr 09, 2015, Marcel Holtmann wrote:
> The Intel vendors events indicating firmware loading result and the
> bootup of the operational firmware are currently hardcoded byte
> comparisons. So intead of doing that, provide proper data structures
> and actually use them.
> 
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>  drivers/bluetooth/btintel.h | 15 +++++++++
>  drivers/bluetooth/btusb.c   | 79 ++++++++++++++++++++++++++++++---------------
>  2 files changed, 68 insertions(+), 26 deletions(-)

Applied to bluetooth-next. Thanks.

Johan

      reply	other threads:[~2015-04-09  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  7:35 [PATCH v3] Bluetooth: btusb: Use proper data structures for Intel vendor events Marcel Holtmann
2015-04-09  7:42 ` 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=20150409074238.GA27217@t440s.lan \
    --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).