From: Akira Yokosawa <akiyks@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] string: Rewrite and add more kern-doc for the str*() functions
Date: Sat, 24 Sep 2022 11:31:16 +0900 [thread overview]
Message-ID: <d9e15a0b-0ec9-894b-b0a6-3425af2ddeff@gmail.com> (raw)
In-Reply-To: <20220922062817.2283352-1-keescook@chromium.org>
Hi Kees,
On Wed, 21 Sep 2022 23:28:17 -0700, Kees Cook wrote:
> While there were varying degrees of kern-doc for various str*()-family
> functions, many needed updating and clarification, or to just be
> entirely written. Update (and relocate) existing kern-doc and add missing
> functions, sadly shaking my head at how many times I have written "Do
> not use this function". Include the results in the core kernel API doc.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Follow up to https://lore.kernel.org/lkml/20220902223507.2537469-1-keescook@chromium.org
> Note that this is on top of my recent fortify-string.h series:
> https://lore.kernel.org/lkml/20220920192202.190793-1-keescook@chromium.org/
I wanted to test this change, but I've not able to find a good commit
where the fortify-string.h series and this one can be applied cleanly.
Would you mind creating a topic branch somewhere on your git tree
and sharing it?
Regards,
Akira
> ---
> Documentation/core-api/kernel-api.rst | 3 +
> include/linux/fortify-string.h | 133 ++++++++++++++++++++++++--
> lib/string.c | 82 ----------------
> scripts/kernel-doc | 4 +
> 4 files changed, 130 insertions(+), 92 deletions(-)
>
[...]
next prev parent reply other threads:[~2022-09-24 2:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 6:28 Kees Cook
2022-09-24 2:31 ` Akira Yokosawa [this message]
2022-09-24 4:24 ` Kees Cook
2022-09-24 7:13 ` Akira Yokosawa
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=d9e15a0b-0ec9-894b-b0a6-3425af2ddeff@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=mchehab@kernel.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®