linux-kernel - Re: [PATCH 3.19.0-rc5 01/02] STAGING: Fix pcl818.c coding style issue: code indent should use tabs where possible

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: <54C7B6D9.3080306@mev.co.uk>
Date:	Tue, 27 Jan 2015 16:03:37 +0000
From:	Ian Abbott <abbotti@....co.uk>
To:	Simon Guo <wei.guo.simon@...il.com>,
	H Hartley Sweeten <hsweeten@...ionengravers.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3.19.0-rc5 01/02] STAGING: Fix pcl818.c coding style issue:
 code indent should use tabs where possible

[Stripped a non-fully-qualified 'To:' address from the reply.]

On 26/01/15 16:58, Simon Guo wrote:
>
> Correct one coding style problem(detected by checkpatch.pl) in pcl818.c.
> - code indent should use tabs where possible
> It is fixed by reformatting the comment block to usual comment style.
>
> And with the reformatting, following coding style problem is also fixed:
> - please, no space before tabs
>
> Signed-off-by: Simon Guo <wei.guo.simon@...il.com>
> ---
>   drivers/staging/comedi/drivers/pcl818.c | 189 +++++++++++++++-----------------
>   1 file changed, 91 insertions(+), 98 deletions(-)

Reviewed-by: Ian Abbott <abbotti@....co.uk>

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@....co.uk> )=-
-=(                          Web: http://www.mev.co.uk/  )=-
--
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/