From: Jonathan Corbet <corbet@lwn.net>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Security: Documentation: fix: `make htmldocs` warnings
Date: Mon, 6 Jul 2020 12:14:07 -0600 [thread overview]
Message-ID: <20200706121407.6c24f537@lwn.net> (raw)
In-Reply-To: <20200706180010.29032-1-puranjay12@gmail.com>
On Mon, 6 Jul 2020 23:30:10 +0530
Puranjay Mohan <puranjay12@gmail.com> wrote:
> Remove extra ')' after function name to fix warnings.
> It solves following warning :
> WARNING: Unparseable C cross-reference: 'groups_sort)'
> Invalid C declaration: Expected end of definition. [error at 11]
>
> Signed-off-by: Puranjay Mohan <puranjay12@gmail.com>
> ---
> Documentation/security/credentials.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/security/credentials.rst b/Documentation/security/credentials.rst
> index 282e79feee6a..d51e42b92395 100644
> --- a/Documentation/security/credentials.rst
> +++ b/Documentation/security/credentials.rst
> @@ -455,7 +455,7 @@ When replacing the group list, the new list must be sorted before it
> is added to the credential, as a binary search is used to test for
> membership. In practice, this means :c:func:`groups_sort` should be
> called before :c:func:`set_groups` or :c:func:`set_current_groups`.
> -:c:func:`groups_sort)` must not be called on a ``struct group_list`` which
> +:c:func:`groups_sort` must not be called on a ``struct group_list`` which
> is shared as it may permute elements as part of the sorting process
> even if the array is already sorted.
So this is a great fix, thanks for sending it. That said, there are a
couple of ways in which this fix can be made even better:
- The simpler of the two is to change the subject line of the patch.
"Fix a warning" is almost never a good description of what you're
doing; what you are actually doing is fixing a broken cross reference.
So the subject line should say that.
- In this case, though, there is a much better thing to do. We
deprecated the use of :c:func: around a year ago; the docs build system
can now do the right thing automatically. So a fix that would both
eliminate the warning and improve the document as a whole would be to
replace every instance of:
:c:func:`function_name`
with:
function_name()
Is there any chance I could get you to send a patch that does that?
Thanks,
jon
next prev parent reply other threads:[~2020-07-06 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 18:00 [PATCH] Security: Documentation: fix: `make htmldocs` warnings Puranjay Mohan
2020-07-06 18:14 ` Jonathan Corbet [this message]
2020-07-06 18:21 ` Puranjay Mohan
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=20200706121407.6c24f537@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=skhan@linuxfoundation.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