From: Marcel Holtmann <marcel@holtmann.org>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: Re: [RFC v4 2/3] Bluetooth: Fix minor coding style in hci_event.c
Date: Thu, 09 Aug 2012 08:50:58 -0700 [thread overview]
Message-ID: <1344527458.2083.55.camel@aeonflux> (raw)
In-Reply-To: <1344498750-2698-3-git-send-email-mikel.astiz.oss@gmail.com>
Hi Mikel,
> Replace the status checks with the short form of the boolean expression.
>
> Signed-off-by: Mikel Astiz <mikel.astiz@bmw-carit.de>
> ---
> net/bluetooth/hci_event.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2012-08-09 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 7:52 [RFC v4 0/3] Disconnect reason in Kernel API Mikel Astiz
2012-08-09 7:52 ` [RFC v4 1/3] Bluetooth: Add more HCI error codes Mikel Astiz
2012-08-09 7:52 ` [RFC v4 2/3] Bluetooth: Fix minor coding style in hci_event.c Mikel Astiz
2012-08-09 15:50 ` Marcel Holtmann [this message]
2012-08-09 7:52 ` [RFC v4 3/3] Bluetooth: mgmt: Add device disconnect reason Mikel Astiz
2012-08-09 15:54 ` Marcel Holtmann
2012-08-15 4:32 ` Gustavo Padovan
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=1344527458.2083.55.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz.oss@gmail.com \
--cc=mikel.astiz@bmw-carit.de \
/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).