From: Luis Chamberlain <mcgrof@kernel.org>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
live-patching@vger.kernel.org, linux-doc@vger.kernel.org,
jpoimboe@kernel.org, mbenes@suse.cz, joe.lawrence@redhat.com,
corbet@lwn.net, pmladek@suse.com
Subject: Re: [PATCH v2] Document klp_modinfo using kdoc
Date: Mon, 6 Feb 2023 09:09:12 -0800 [thread overview]
Message-ID: <Y+E0OKpt1I5pLA8C@bombadil.infradead.org> (raw)
In-Reply-To: <20230203122222.1907-1-mpdesouza@suse.com>
On Fri, Feb 03, 2023 at 09:22:20AM -0300, Marcos Paulo de Souza wrote:
> Originally it was only one patch, but it was divided in two. The second one
> removed the local declaration to klp_modinfo and also refers to it using kdoc
> format.
>
> Changes from v1:
> * Use kdoc (Luis)
>
> Original commit message:
> The struct members description can be found on
> Documentation/livepatch/module-elf-format.rst, but for a developer it's
> easier to search for such information looking at the struct definition.
>
> Marcos Paulo de Souza (2):
> module.h: Document klp_modinfo struct using kdoc
> Documentation: livepatch: module-elf-format: Remove local klp_modinfo
> definition
Thanks! Merged and pushed onto modules-next! If you can get more modules
stuff into kdoc that would be appreciated!
Luis
prev parent reply other threads:[~2023-02-06 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:22 [PATCH v2] Document klp_modinfo using kdoc Marcos Paulo de Souza
2023-02-03 12:22 ` [PATCH v2 1/2] module.h: Document klp_modinfo struct " Marcos Paulo de Souza
2023-02-03 12:22 ` [PATCH v2 2/2] Documentation: livepatch: module-elf-format: Remove local klp_modinfo definition Marcos Paulo de Souza
2023-02-06 17:09 ` Luis Chamberlain [this message]
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=Y+E0OKpt1I5pLA8C@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=corbet@lwn.net \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=pmladek@suse.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 read-only IMAP folder(s) and NNTP newsgroup(s).