From: Marcel Holtmann <marcel@holtmann.org>
To: Andre Guedes <aguedespe@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, andre.guedes@openbossa.org
Subject: Re: [PATCH 2/2] Bluetooh: Fix hci_cc_read_local_ext_features()
Date: Fri, 30 Dec 2011 11:17:15 -0800 [thread overview]
Message-ID: <1325272635.1965.297.camel@aeonflux> (raw)
In-Reply-To: <1325252044-21134-2-git-send-email-aguedespe@gmail.com>
Hi Andre,
> Copy the Features value according to the Page number.
>
> Signed-off-by: Andre Guedes <aguedespe@gmail.com>
> ---
> net/bluetooth/hci_event.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 37c31c5..10152d2 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -711,7 +711,14 @@ static void hci_cc_read_local_ext_features(struct hci_dev *hdev,
> if (rp->status)
> return;
>
> - memcpy(hdev->host_features, rp->features, 8);
> + switch (rp->page) {
> + case 0:
> + memcpy(hdev->features, rp->features, 8);
> + break;
> + case 1:
> + memcpy(hdev->host_features, rp->features, 8);
> + break;
> + }
>
> hci_req_complete(hdev, HCI_OP_READ_LOCAL_EXT_FEATURES, rp->status);
> }
I was fine with just handling page 1 properly since we do not use
read_local_ext_features for page 0 in the first place. However this is
also fine with me.
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2011-12-30 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 13:34 [PATCH 1/2] Bluetooth: Rename extfeatures Andre Guedes
2011-12-30 13:34 ` [PATCH 2/2] Bluetooh: Fix hci_cc_read_local_ext_features() Andre Guedes
2011-12-30 19:17 ` Marcel Holtmann [this message]
2012-01-03 0:23 ` Gustavo Padovan
2011-12-30 19:15 ` [PATCH 1/2] Bluetooth: Rename extfeatures 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=1325272635.1965.297.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=aguedespe@gmail.com \
--cc=andre.guedes@openbossa.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox