Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bing Zhao <bzhao@marvell.com>
Cc: "linux-bluetooth@vger.kernel.org development"
	<linux-bluetooth@vger.kernel.org>,
	"Gustavo F. Padovan" <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Mike Frysinger <vapier@chromium.org>,
	Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH 3/3] Bluetooth: btmrvl: operate on 16-bit opcodes instead of ogf/ocf
Date: Fri, 1 Nov 2013 23:33:54 +0100	[thread overview]
Message-ID: <758D809C-CDC1-46FD-8F61-3465C90DBF11@holtmann.org> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430F45757D88@SC-VEXCH1.marvell.com>

Hi Bing,

>>> Replace ogf/ocf and its packing with 16-bit opcodes.
>>> 
>>> Signed-off-by: Bing Zhao <bzhao@marvell.com>
>>> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
>>> ---
>>> drivers/bluetooth/btmrvl_drv.h  | 19 +++++++++++--------
>>> drivers/bluetooth/btmrvl_main.c | 21 +++++++++------------
>>> 2 files changed, 20 insertions(+), 20 deletions(-)
>> 
>> patch looks fine to me. Since you send it as 3/3, I don’t know if you want me to apply it right away
>> or just when the whole series is ready to be applied.
> 
> Please apply 3/3 first if that's convenient for you.
> I will resend 1/3 and 2/3 in v2 series.

patch has been applied to bluetooth-next tree.

Regards

Marcel


  reply	other threads:[~2013-11-01 22:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 22:08 [PATCH 1/3] Bluetooth: btmrvl: use cal-data from device-tree instead of conf file Bing Zhao
2013-10-31 22:08 ` [PATCH 2/3] Bluetooth: btmrvl: remove cal-data byte swapping and redundant mem copy Bing Zhao
2013-10-31 22:08 ` [PATCH 3/3] Bluetooth: btmrvl: operate on 16-bit opcodes instead of ogf/ocf Bing Zhao
2013-11-01 21:36   ` Marcel Holtmann
2013-11-01 22:11     ` Bing Zhao
2013-11-01 22:33       ` Marcel Holtmann [this message]
2013-11-01 21:33 ` [PATCH 1/3] Bluetooth: btmrvl: use cal-data from device-tree instead of conf file Marcel Holtmann
2013-11-01 22:08   ` Bing Zhao
2013-11-01 22:21     ` Marcel Holtmann

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=758D809C-CDC1-46FD-8F61-3465C90DBF11@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=akarwar@marvell.com \
    --cc=bzhao@marvell.com \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vapier@chromium.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