From: Michal Simek <monstr@monstr.eu>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] coverity, static checking etc.
Date: Mon, 19 May 2014 12:13:50 +0200 [thread overview]
Message-ID: <5379D95E.7080003@monstr.eu> (raw)
In-Reply-To: <20140518133839.487d811a.m.chehab@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Hi Mauro
On 05/18/2014 06:38 PM, Mauro Carvalho Chehab wrote:
> Em Mon, 12 May 2014 08:48:11 +0200
> Michal Simek <monstr@monstr.eu> escreveu:
>
>> The part of this discussion
>> should be also kernel-doc format checking because a lot of patches
>> are trying to use kernel-doc format but it is just broken - even checker
>> is in the kernel.
>
> There are several drivers still using other styles for documenting functions.
>
> I can be partially blamed for accepting such patches, but, I don't feel
> it is fair to refuse merging a patchset just because they're following some
> other documentation style. We have some really big drivers at media
> ported from another OS using Doxygen style. Fixing them would likely
> require hundreds of hours that could otherwise be used implementing
> new stuff or fixing real bugs.
>
> So, I would rather prefer to have a (semi-)automated tool capable of
> converting from Doxygen and other styles into kernel-doc style that
> would make such conversion an easy task.
I have no experience with Doxygen but I can't see any problem.
If Doxygen is used in the kernel in any subsystem then it should
be checked if possible.
I am not definitely saying - use kernel-doc everywhere.
But I am saying when you use kernel-doc format it should be used
and checked properly.
The same is for Doxygen and others.
Warning/error should be checked and if there is any problem patch
should be rejected.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-05-19 10:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 17:07 [Ksummit-discuss] coverity, static checking etc Dave Jones
2014-05-09 17:19 ` josh
2014-05-09 17:31 ` Johannes Berg
2014-05-09 17:54 ` Guenter Roeck
2014-05-09 18:04 ` Mark Brown
2014-05-09 19:08 ` Jiri Kosina
2014-05-09 19:41 ` Dmitry Torokhov
2014-05-09 19:29 ` Josh Triplett
2014-05-09 17:37 ` Bjorn Helgaas
2014-05-09 20:18 ` Arnd Bergmann
2014-05-09 20:33 ` Dave Jones
2014-05-09 21:39 ` Arnd Bergmann
2014-05-09 20:33 ` Roland Dreier
2014-05-09 20:52 ` Dave Jones
2014-05-09 20:57 ` tytso
2014-05-14 11:06 ` Dan Carpenter
2014-05-11 11:10 ` Wolfram Sang
2014-05-12 6:48 ` Michal Simek
2014-05-12 9:32 ` Wolfram Sang
2014-05-14 11:09 ` Dan Carpenter
2014-05-14 13:32 ` Johannes Berg
2014-05-14 13:51 ` Guenter Roeck
2014-05-14 15:22 ` Wolfram Sang
2014-05-14 15:44 ` Peter Huewe
2014-05-14 16:36 ` Wolfram Sang
2014-05-18 16:38 ` Mauro Carvalho Chehab
2014-05-19 10:13 ` Michal Simek [this message]
2014-05-12 8:58 ` Peter Senna Tschudin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5379D95E.7080003@monstr.eu \
--to=monstr@monstr.eu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=m.chehab@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.