Search Linux Wireless

Re: [PATCH 01/14] cw1200: v4: low-level hardware I/O functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Joe Perches <joe@xxxxxxxxxxx> writes:

>> Question -- as a matter of policy, is the goal to have a completely 
>> clean checkpatch run?  I get that there should be no ERRORs, but 
>> WARNINGs/CHECKs are not considered fatal for a reason, right?
>
> No.  It's just a guideline.  As far as I'm concerned,
> ignore every checkpatch message you don't agree with.

BTW, I think this is becoming a major problem. I have had discussions
with various people who consider checkpatch as some sort of automatic
upstream compliance system. I'm a bit worried about that. People should
consider just as a tool next to other tools, not as the holy bible.

Joe, when working with checkpatch documentation you could try to
emphasise that part (or it might be that you have already done that).

Just my 0.02 EUR.

-- 
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux