From: Paul McQuade <paulmcquad@gmail.com>
To: paulmcquad@gmail.com
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] Bluetooth: Use tabs where possible
Date: Mon, 19 Mar 2018 11:32:20 +0000 [thread overview]
Message-ID: <20180319113222.6725-2-paulmcquad@gmail.com> (raw)
In-Reply-To: <20180319113222.6725-1-paulmcquad@gmail.com>
code indent should use tabs where possible
Signed-off-by: Paul McQuade <paulmcquad@gmail.com>
---
drivers/bluetooth/hci_intel.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/bluetooth/hci_intel.c b/drivers/bluetooth/hci_intel.c
index 7c166e3b308b..2a7bdc0bad92 100644
--- a/drivers/bluetooth/hci_intel.c
+++ b/drivers/bluetooth/hci_intel.c
@@ -609,12 +609,12 @@ static int intel_setup(struct hci_uart *hu)
return -EINVAL;
}
- /* Check for supported iBT hardware variants of this firmware
- * loading method.
- *
- * This check has been put in place to ensure correct forward
- * compatibility options when newer hardware variants come along.
- */
+ /* Check for supported iBT hardware variants of this firmware
+ * loading method.
+ *
+ * This check has been put in place to ensure correct forward
+ * compatibility options when newer hardware variants come along.
+ */
switch (ver.hw_variant) {
case 0x0b: /* LnP */
case 0x0c: /* WsP */
--
2.16.2
next prev parent reply other threads:[~2018-03-19 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 11:32 [PATCH 1/4] Bluetooth: trailing whitespace Paul McQuade
2018-03-19 11:32 ` Paul McQuade [this message]
2018-03-19 11:32 ` [PATCH 3/4] Bluetooth: trailing statements Paul McQuade
2018-03-20 8:09 ` Marcel Holtmann
2018-03-19 11:32 ` [PATCH 4/4] Bluetooth: space required Paul McQuade
2018-03-20 8:10 ` [PATCH 1/4] Bluetooth: trailing whitespace 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=20180319113222.6725-2-paulmcquad@gmail.com \
--to=paulmcquad@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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).