linux-kernel - [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes

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: <1426712196-7288-1-git-send-email-janakarajann@gmail.com>
Date:	Wed, 18 Mar 2015 13:56:31 -0700
From:	Janakarajan Natarajan <janakarajann@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Joe Perches <joe@...ches.com>, devel@...verdev.osuosl.org
Cc:	Marek Belisko <marek.belisko@...il.com>,
	linux-kernel@...r.kernel.org,
	Janakarajan Natarajan <janakarajann@...il.com>
Subject: [PATCHv2 0/5] ft1000 driver checkpatch.pl fixes

Minor changes to fix ft1000 driver checkpatch.pl warnings

Janakarajan Natarajan (5):
  Drivers: Staging: ft1000: Single line if-statement changes
  Drivers: Staging: ft1000: Fix extra parenthesis warnings
  Drivers: Staging: ft1000: Refactoring if-else statement
  Drivers: Staging: ft1000: Fix blank line after declartion warning
  Drivers: Staging: ft1000: checkpatch.pl header file warning fix

v2: if-else refactored as suggested by Joe Perches <joe@...ches.co
    Variable reworked as suggested by Giedrius Statkevicius <giedrius.statkevicius@...il.com>

 drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c | 16 +++++++---------
 drivers/staging/ft1000/ft1000-usb/ft1000_debug.c |  6 ++----
 2 files changed, 9 insertions(+), 13 deletions(-)

-- 
1.9.1


---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

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