From: t.a.c.henriques@googlemail.com
To: gregkh@suse.de, t.a.c.henriques@gmail.com
Cc: marcel@holtmann.org, adobriyan@gmail.com, tglx@linutronix.de,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Bluetooth: fix coding style issue in hci_vhci.c This patch affects hci_vhci.c it fixes some warnings detected by the checkpath.pl tool Signed-off-by: Tiago Henriques <t.a.c.henriques@gmail.com>
Date: Sun, 7 Mar 2010 04:03:51 +0000 [thread overview]
Message-ID: <1267934631-3531-1-git-send-email-t.a.c.henriques@gmail.com> (raw)
In-Reply-To: <Fix Bluetooth Code Style warnings>
From: root <root@balganUbuntuVM.(none)>
---
drivers/bluetooth/hci_vhci.c | 7 ++-----
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/bluetooth/hci_vhci.c b/drivers/bluetooth/hci_vhci.c
index bb0aefd..4a5386e 100644
--- a/drivers/bluetooth/hci_vhci.c
+++ b/drivers/bluetooth/hci_vhci.c
@@ -264,12 +264,9 @@ static int vhci_release(struct inode *inode, struct file *file)
struct vhci_data *data = file->private_data;
struct hci_dev *hdev = data->hdev;
- if (hci_unregister_dev(hdev) < 0) {
+ if (hci_unregister_dev(hdev) < 0)
BT_ERR("Can't unregister HCI device %s", hdev->name);
- }
-
hci_free_dev(hdev);
-
file->private_data = NULL;
return 0;
@@ -284,7 +281,7 @@ static const struct file_operations vhci_fops = {
.release = vhci_release,
};
-static struct miscdevice vhci_miscdev= {
+static struct miscdevice vhci_miscdev = {
.name = "vhci",
.fops = &vhci_fops,
.minor = MISC_DYNAMIC_MINOR,
--
1.6.3.3
next parent reply other threads:[~2010-03-07 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Fix Bluetooth Code Style warnings>
2010-03-07 4:03 ` t.a.c.henriques [this message]
2010-03-07 15:56 ` Greg KH
2010-03-07 21:08 ` Marcel Holtmann
2010-03-07 23:27 ` Greg KH
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=1267934631-3531-1-git-send-email-t.a.c.henriques@gmail.com \
--to=t.a.c.henriques@googlemail.com \
--cc=adobriyan@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=t.a.c.henriques@gmail.com \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®