All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Kees Cook <keescook@chromium.org>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-hardening@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Yanteng Si <siyanteng@loongson.cn>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	linux-kernel@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2] overflow: Fix kern-doc markup for functions
Date: Tue, 18 Oct 2022 10:11:43 +0900	[thread overview]
Message-ID: <6f8aa670-fb4f-3ff9-bcd9-8490e752b349@gmail.com> (raw)
In-Reply-To: <20221017035732.1968394-1-keescook@chromium.org>

Hi,

On Sun, 16 Oct 2022 20:57:32 -0700, Kees Cook wrote:
> Fix the kern-doc markings for several of the overflow helpers and move
> their location into the core kernel API documentation, where it belongs
> (it's not driver-specific).
> 
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Akira Yokosawa <akiyks@gmail.com>
LGTM,

Reviewed-by: Akira Yokosawa <akiyks@gmail.com>

Kees, which tree do you expect this one to go through?

        Thanks, Akira

> Cc: linux-doc@vger.kernel.org
> Cc: linux-hardening@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
>  Documentation/core-api/kernel-api.rst |  6 +++++
>  Documentation/driver-api/basics.rst   |  3 ---
>  include/linux/overflow.h              | 38 +++++++++++----------------
>  3 files changed, 22 insertions(+), 25 deletions(-)
> 


  reply	other threads:[~2022-10-18  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  3:57 [PATCH v2] overflow: Fix kern-doc markup for functions Kees Cook
2022-10-18  1:11 ` Akira Yokosawa [this message]
2022-10-18  2:09   ` Kees Cook
2022-10-18 13:48     ` Jonathan Corbet

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=6f8aa670-fb4f-3ff9-bcd9-8490e752b349@gmail.com \
    --to=akiyks@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=corbet@lwn.net \
    --cc=djwong@kernel.org \
    --cc=johannes.thumshirn@wdc.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=siyanteng@loongson.cn \
    --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 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.