linux-kernel - [PATCH 2/4] Staging: lustre: namei.c: fix "foo * bar" should be "foo *bar"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1426704587-11811-2-git-send-email-maxime.lorrillere@lip6.fr>
Date:	Wed, 18 Mar 2015 19:49:46 +0100
From:	Maxime Lorrillere <maxime.lorrillere@...6.fr>
To:	andreas.dilger@...el.com, gregkh@...uxfoundation.org
Cc:	linux-kernel@...r.kernel.org, laure.millet@...6.fr,
	maxime.lorrillere@...6.fr
Subject: [PATCH 2/4] Staging: lustre: namei.c: fix  "foo * bar" should be "foo *bar"

From: Laure Millet <laure.millet@...6.fr>

This patch fixes a coding style error in a pointer declaration.

Signed-off-by: Laure Millet <laure.millet@...6.fr>
Signed-off-by: Maxime Lorrillere <maxime.lorrillere@...6.fr>
---
 drivers/staging/lustre/lustre/llite/namei.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/lustre/lustre/llite/namei.c b/drivers/staging/lustre/lustre/llite/namei.c
index 992f3f0..477dae1 100644
--- a/drivers/staging/lustre/lustre/llite/namei.c
+++ b/drivers/staging/lustre/lustre/llite/namei.c
@@ -974,7 +974,7 @@ out:
  * Instead, ll_ddelete() and ll_d_iput() will update it based upon if there
  * is any lock existing. They will recycle dentries and inodes based upon locks
  * too. b=20433 */
-static int ll_unlink(struct inode * dir, struct dentry *dentry)
+static int ll_unlink(struct inode *dir, struct dentry *dentry)
 {
 	struct ptlrpc_request *request = NULL;
 	struct md_op_data *op_data;
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/