From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/4] Bluetooth: Fix type in cpu_to_le conversion
Date: Mon, 12 Mar 2012 10:35:27 -0700 [thread overview]
Message-ID: <1331573727.14217.80.camel@aeonflux> (raw)
In-Reply-To: <1331560774-10748-2-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> Use struct hci_cp_write_def_link_policy to overcome sparse
> warnigs below:
>
> ...
> net/bluetooth/hci_event.c:633:21: warning: incorrect type in assignment
> (different base types)
> net/bluetooth/hci_event.c:633:21: expected unsigned short [unsigned]
> [assigned] [usertype] link_policy
> net/bluetooth/hci_event.c:633:21: got restricted __le16 [usertype] <noident>
> ...
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/hci_event.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2012-03-12 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 13:59 [PATCH 1/4] Bluetooth: trivial: Correct types Andrei Emeltchenko
2012-03-12 13:59 ` [PATCH 2/4] Bluetooth: Fix type in cpu_to_le conversion Andrei Emeltchenko
2012-03-12 17:35 ` Marcel Holtmann [this message]
2012-03-12 13:59 ` [PATCH 3/4] Bluetooth: Fix opcode access in hci_complete Andrei Emeltchenko
2012-03-12 17:38 ` Marcel Holtmann
2012-03-12 13:59 ` [PATCH 4/4] Bluetooth: trivial: Remove sparse warnings Andrei Emeltchenko
2012-03-12 17:36 ` Marcel Holtmann
2012-03-13 8:16 ` Andrei Emeltchenko
2012-03-12 17:39 ` [PATCH 1/4] Bluetooth: trivial: Correct types Marcel Holtmann
2012-03-16 15:36 ` Johan Hedberg
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=1331573727.14217.80.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).