Live Patching
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] module.h: Document klp_modinfo struct members
Date: Thu, 2 Feb 2023 11:02:27 -0800	[thread overview]
Message-ID: <Y9wIw3f8IBOs4Ad6@bombadil.infradead.org> (raw)
In-Reply-To: <20230202182950.10471-1-mpdesouza@suse.com>

On Thu, Feb 02, 2023 at 03:29:50PM -0300, Marcos Paulo de Souza wrote:
> 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.
> 
> Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>

Why not just embrace kdoc and then refer to it in the rst files?

  Luis

  reply	other threads:[~2023-02-02 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 18:29 [PATCH] module.h: Document klp_modinfo struct members Marcos Paulo de Souza
2023-02-02 19:02 ` Luis Chamberlain [this message]
2023-02-02 19:07   ` Marcos Paulo de Souza

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=Y9wIw3f8IBOs4Ad6@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mpdesouza@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