linux-kernel - Re: [PATCH 3/5 v2] Staging: cxt1e1: Fix line length over 80 characters in hwprobe.c

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]

Date:	Tue, 04 Mar 2014 07:40:40 +0100
From:	khalasa@...p.pl (Krzysztof Hałasa)
To:	DaeSeok Youn <daeseok.youn@...il.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	"sachin.kamat" <sachin.kamat@...aro.org>,
	Shaun Laing <shaun@...source.ca>,
	Dulshani Gunawardhana <dulshani.gunawardhana89@...il.com>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	devel <devel@...verdev.osuosl.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/5 v2] Staging: cxt1e1: Fix line length over 80 characters in hwprobe.c

DaeSeok Youn <daeseok.youn@...il.com> writes:

>>> -              * match with board's first found interface, otherwise this is first
>>> -              * found
>>> +              * match with board's first found interface, otherwise this is
>>> +              * fisrt found
>>                    ^^^^^
>> I wonder what's your exact procedure for doing such changes :-)
> "first" word is over 80 line character after applying my previous patch(2/5)
> (previous patch is already merged to staging-next tree :-))

Sure, I meant I'd just break the line without re-typing the first/fisrt
word manually... Never mind.

Anyway, I'd rather aim for improving overall code quality, not just
silence 80-char warning. I'm not a big fan of this warning.
-- 
Krzysztof Halasa

Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
--
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/