linux-kernel - [PATCH] Staging: clocking-wizard: Added a blank line after declaration

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

Message-Id: <1419129228-5333-1-git-send-email-md.jamalmohiuddin@gmail.com>
Date:	Sun, 21 Dec 2014 08:03:48 +0530
From:	Mohammad Jamal <md.jamalmohiuddin@...il.com>
To:	gregkh@...uxfoundation.org
Cc:	soren.brinkmann@...inx.com, laurent.pinchart@...asonboard.com,
	md.jamalmohiuddin@...il.com, devendra.aaru@...il.com,
	athirasnamby@...il.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH] Staging: clocking-wizard: Added a blank line after declaration

Fix the coding style issue by adding blank line after declaration

Signed-off-by: Mohammad Jamal <md.jamalmohiuddin@...il.com>
---
 .../clocking-wizard/clk-xlnx-clock-wizard.c        |    1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c b/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c
index 471d087..ea8d561 100644
--- a/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c
+++ b/drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.c
@@ -239,6 +239,7 @@ static int clk_wzrd_probe(struct platform_device *pdev)
 	/* register div per output */
 	for (i = WZRD_NUM_OUTPUTS - 1; i >= 0 ; i--) {
 		const char *clkout_name;
+
 		if (of_property_read_string_index(np, "clock-output-names", i,
 						  &clkout_name)) {
 			dev_err(&pdev->dev,
-- 
1.7.9.5

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