From: Akira Yokosawa <akiyks@gmail.com>
To: Kees Cook <keescook@chromium.org>, Matthew Wilcox <willy@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] overflow: Fix kern-doc markup for functions
Date: Tue, 27 Sep 2022 11:53:38 +0900 [thread overview]
Message-ID: <ada70afe-64d5-ccab-242e-9a3c3c85e6c4@gmail.com> (raw)
In-Reply-To: <202209261408.59F78C0D@keescook>
Hi,
Somehow Kees added me in Cc:, so let me comment. :-)
On Mon, 26 Sep 2022 14:09:10 -0700, Kees Cook wrote:
> On Mon, Sep 26, 2022 at 10:06:19PM +0100, Matthew Wilcox wrote:
>> On Mon, Sep 26, 2022 at 12:47:13PM -0700, Kees Cook wrote:
>>> -/** check_add_overflow() - Calculate addition with overflow checking
>>> +/**
>>> + * check_add_overflow - Calculate addition with overflow checking
>>> *
>>> * @a: first addend
>>> * @b: second addend
>>
>> Why did you remove the ()? And why didn't you delete the blank line?
>> According to our documentation, the canonical form is:
>>
>> /**
>> * function_name() - Brief description of function.
>> * @arg1: Describe the first argument.
>> * @arg2: Describe the second argument.
>> * One can provide multiple line descriptions
>> * for arguments.
Matthew, you call it the "canonical form", my take is more of a "template
that is known to work".
>>
>> I don't usually complain about people getting that wrong, but when
>> people correct it to be wrong ...
I'd say "wrong" if "./scripts/kernel-doc -v -none include/linux/overflow.h"
complained or the resulting reST doc didn't rendered properly, but that's
not the case here.
>
> Hunh, everywhere I'd looked didn't have the "()" (which seems
> redundant). The blank line was entirely aesthetics for me. If it's
> supposed to be without a blank, I can fix it up everwhere.
So, I think this is more of a territory of preference or consistency
rather than that of correctness. Those extra blank lines can be confusing
as most people expect it in front of description part.
get_maintainer.pl says Kees is the sole maintainer of overflow.h, so
it's his call, I guess.
Thanks, Akira
>
next prev parent reply other threads:[~2022-09-27 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 19:47 Kees Cook
2022-09-26 21:06 ` Matthew Wilcox
2022-09-26 21:09 ` Kees Cook
2022-09-27 2:53 ` Akira Yokosawa [this message]
2022-09-27 3:02 ` Kees Cook
2022-09-27 10:35 ` Akira Yokosawa
2022-09-27 8:32 ` Bagas Sanjaya
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=ada70afe-64d5-ccab-242e-9a3c3c85e6c4@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®