From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/4] padata: update documentation
Date: Wed, 20 Nov 2019 12:16:34 -0700 [thread overview]
Message-ID: <20191120121634.6d989088@lwn.net> (raw)
In-Reply-To: <20191120185412.302-2-daniel.m.jordan@oracle.com>
On Wed, 20 Nov 2019 13:54:09 -0500
Daniel Jordan <daniel.m.jordan@oracle.com> wrote:
> Remove references to unused functions and update to reflect the new
> struct padata_shell.
>
> Fixes: 815613da6a67 ("kernel/padata.c: removed unused code")
> Signed-off-by: Daniel Jordan <daniel.m.jordan@oracle.com>
> Cc: Eric Biggers <ebiggers@kernel.org>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>
> Cc: linux-crypto@vger.kernel.org
> Cc: linux-doc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> Documentation/padata.txt | 50 +++++++++++++++++++++-------------------
> 1 file changed, 26 insertions(+), 24 deletions(-)
This all seems fine - it's better than not doing it - but can I put in a
request or two?
- This document is already formatted as RST, and your changes continue
that. Can we please move it to Documentation/core-api/padata.rst and
add it to the TOC tree there? Then it can become part of our formatted
docs.
- The padata code seems to be nicely equipped with kerneldoc comments; it
would be awfully nice to pull them into the document directly rather
than replicating the API there. (Why does the document do that now?
Blame the bozo who originally wrote it :) That would make the document
more complete and easier to maintain going forward.
For added goodness we could stick in an SPDX tag while we're at it.
Thanks,
jon
next prev parent reply other threads:[~2019-11-20 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191120185412.302-1-daniel.m.jordan@oracle.com>
2019-11-20 18:54 ` [PATCH 1/4] padata: update documentation Daniel Jordan
2019-11-20 19:16 ` Jonathan Corbet [this message]
2019-11-21 14:36 ` Daniel Jordan
2019-11-20 18:54 ` [PATCH 4/4] padata: remove cpumask change notifier Daniel Jordan
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=20191120121634.6d989088@lwn.net \
--to=corbet@lwn.net \
--cc=daniel.m.jordan@oracle.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steffen.klassert@secunet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).