linux-kernel - Re: Checkpatch problem with Kconfig help symbol ?

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, 1 Feb 2011 14:11:35 +0200
From:	Tomas Winkler <tomasw@...il.com>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Andy Whitcroft <apw@...onical.com>, tapio.vihuri@...ia.com,
	ext Michal Marek <mmarek@...e.cz>,
	WANG Cong <xiyou.wangcong@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Checkpatch problem with Kconfig help symbol ?

On Tue, Feb 1, 2011 at 1:00 AM, Andi Kleen <ak@...ux.intel.com> wrote:
> Tomas Winkler <tomasw@...il.com> writes:
>
>>>
>>> Yeah that is a little better.  I do remind you that if the description
>>> is good enough shorter than 4 lines then you can ignore checkpatch.  It
>>> is a style guide not a style enforcer.  You are allowed to ignore things
>>> if you can justify it.
>>
>> Please consider patch I've posted
>> http://marc.info/?l=linux-kernel&m=129647530611677&w=2
>
> I originally didn't put in the number intentionally to make
> it harder to game it. Most likely for a whole driver
> or whole subsystems 4 lines are not enough to describe
> it properly.
>
> But yes if it's just for a debug feature you can ignore it.
> But then most likely your debug feature shouldn't be
> in Kconfig in the first place, but some runtime setting
>
> (rule of thumb: if it controls less than 1KB of code it's
> likely a bad idea in Kconfig)
>
> And more complex debug features that do actually carry
> significant code should have proper description.
>
> I think a better change would be to describe this
> more fully, not add the number.

These are all valid points but current message just leave you puzzled
and you have to look inside checkpatch.pl to figure out what it wants.
I'm not sure how would you lay your thoughts concisely  in one line
warning or script them into the script.

My guess would be that most of the developers  tends to come witch
checkpatch.pl clean and even when you expose the number 4 it still
make them stop and think how to fill them properly. Maybe you can
squeeze into the waring  pointer to CodyingStyle section.

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