linux-kernel - [PATCH] workqueue_internal.h: adjust tab alignment

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>] [day] [month] [year] [list]

Date:	Mon,  5 Jan 2015 16:07:49 +0100
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	tj@...nel.org
Cc:	linux-kernel@...r.kernel.org,
	Valentin Rothberg <valentinrothberg@...il.com>
Subject: [PATCH] workqueue_internal.h: adjust tab alignment

The comment for the current_pwq member in the worker struct has
not been tab aligned, which is inconsistent with the rest of the
code.

Signed-off-by: Valentin Rothberg <valentinrothberg@...il.com>
---
I am currently studying interrupt code. While reading, my eyes stopped at this
line to figure out what's wrong.  I hesitated to send this patch, but I think
it's less confusing (at least for my eyes) now.
---
 kernel/workqueue_internal.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/workqueue_internal.h b/kernel/workqueue_internal.h
index 4521587..3dcd4be 100644
--- a/kernel/workqueue_internal.h
+++ b/kernel/workqueue_internal.h
@@ -28,7 +28,7 @@ struct worker {
 
 	struct work_struct	*current_work;	/* L: work being processed */
 	work_func_t		current_func;	/* L: current_work's fn */
-	struct pool_workqueue	*current_pwq; /* L: current_work's pwq */
+	struct pool_workqueue	*current_pwq;	/* L: current_work's pwq */
 	bool			desc_valid;	/* ->desc is valid */
 	struct list_head	scheduled;	/* L: scheduled works */
 
-- 
1.9.1

--
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/