[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210722153939.08a6853c@hermes.local>
Date: Thu, 22 Jul 2021 15:39:39 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: gregkh@...uxfoundation.org, tj@...nel.org, shuah@...nel.org,
akpm@...ux-foundation.org, rafael@...nel.org, davem@...emloft.net,
kuba@...nel.org, ast@...nel.org, andriin@...com,
daniel@...earbox.net, atenart@...nel.org, alobakin@...me,
weiwan@...gle.com, ap420073@...il.com, jeyu@...nel.org,
ngupta@...are.org, sergey.senozhatsky.work@...il.com,
minchan@...nel.org, axboe@...nel.dk, mbenes@...e.com,
jpoimboe@...hat.com, tglx@...utronix.de, keescook@...omium.org,
jikos@...nel.org, rostedt@...dmis.org, peterz@...radead.org,
linux-block@...r.kernel.org, netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel/module: add documentation for try_module_get()
On Thu, 22 Jul 2021 15:19:05 -0700
Luis Chamberlain <mcgrof@...nel.org> wrote:
> +/**
> + * try_module_get - yields to module removal and bumps reference count otherwise
> + * @module: the module we should check for
You have the right intentions, but this patch needs some work.
This looks like a docbook comment format but isn't that format.
The first couple of lines need to be reworded to be a complete sentence like
the rest.
In general best to make new comments the same as existing comments
in the same area.
It would be better to put this description in the header file where other
docbook comments for module API are. See example around module_init() and module_exit().
Ideally, all the api's around module reference counts would be documented there.
Powered by blists - more mailing lists