All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <dixitparmar19@gmail.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 1/1] documentation: add doc for KERNEL_SPLIT_MODULES
Date: Fri, 06 Jun 2025 10:07:49 +0200	[thread overview]
Message-ID: <DAFAOKE2FWFD.DPMX3RYZP4XR@bootlin.com> (raw)
In-Reply-To: <12982.1749125890901991398@lists.yoctoproject.org>

On Thu Jun 5, 2025 at 2:18 PM CEST, Dixit Parmar via lists.yoctoproject.org wrote:
> Thank you for guidance.
> My idea was to have documentation for KERNEL_SPLIT_MODULES in the
> meta/conf/documentation.conf similar to KERNEL_MODULE_AUTOLOAD,
> KERNEL_MODULE_PROBECONF etc is there in this file. Not sure if that is correct
> understanding. Can you please suggest if we need KERNEL_SPLIT_MODULES in the
> meta/conf/documentation.conf or not apart from having it in the
> variable-glossary.
>
> I'd really appreciate if you could point me to correct mailing list &
> prefix(if needed) for variable glossary.

If you modify meta/conf/documentation.conf, the patch needs to be sent to
openembedded-core@lists.openembedded.org, because that file is part of
openembedded-core.

If you modify the yocto-docs repository, the patch needs to be sent to
docs@lists.yoctoproject.org.

Thanks for contributing!
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-06-06  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  3:22 [PATCH 1/1] documentation: add doc for KERNEL_SPLIT_MODULES Dixit Parmar
2025-06-02  9:27 ` [docs] " Quentin Schulz
2025-06-04  6:33 ` Antonin Godard
2025-06-05 12:18   ` Dixit Parmar
2025-06-06  8:07     ` Antonin Godard [this message]
2025-06-05 13:36   ` Dixit Parmar

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=DAFAOKE2FWFD.DPMX3RYZP4XR@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=dixitparmar19@gmail.com \
    --cc=docs@lists.yoctoproject.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.