Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anis Bougrine <anis.bougrine10@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: antonin.godard@bootlin.com, bruce.ashfield@gmail.com,
	jose.quaresma@oss.qualcomm.com,
	richard.purdie@linuxfoundation.org,
	Anis Bougrine <anis.bougrine10@gmail.com>
Subject: [OE-core][PATCH v4 4/4] documentation.conf: add documentation for MOD_INSTALL_PREFIX variable
Date: Sat, 22 Aug 2026 02:26:01 +0200	[thread overview]
Message-ID: <20260822002601.90667-5-anis.bougrine10@gmail.com> (raw)
In-Reply-To: <20260822002601.90667-1-anis.bougrine10@gmail.com>

Signed-off-by: Anis Bougrine <anis.bougrine10@gmail.com>
---
    changes in v4:
    
    - Re-sign kernel modules after package stripping process
    - Remove package-stripping skip in package.py
    - Add MOD_INSTALL_PREFIX variable
    
    changes in v3:
    
    - Fixing rebase issue.
    
    changes in v2:
    
    - Use the conditional INSTALL_MOD_STRIP environment variable to avoid
      duplicating the oe_runmake call.
    - Use `scripts/config` script instead of grepping .config file.
---
 meta/conf/documentation.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index 72513296e2..453190f024 100644
--- a/meta/conf/documentation.conf
+++ b/meta/conf/documentation.conf
@@ -282,6 +282,7 @@ MAINTAINER[doc] = "The email address of the distribution maintainer."
 MIRRORS[doc] = "Specifies additional paths from which the OpenEmbedded build system gets source code."
 MLPREFIX[doc] = "Specifies a prefix has been added to PN to create a special version of a recipe or package, such as a Multilib version."
 MODULE_TARBALL_DEPLOY[doc] = "Controls creation of the modules-*.tgz file. Set this variable to "0" to disable creation of this file, which contains all of the kernel modules resulting from a kernel build."
+MOD_INSTALL_PREFIX[doc] = "When a recipe inherits the module class, this variable specifies the directory to which kernel modules are installed on target."
 MULTIMACH_TARGET_SYS[doc] = "Separates files for different machines such that you can build for multiple target machines using the same output directories."
 
 #N
-- 
2.50.1 (Apple Git-155)



  parent reply	other threads:[~2026-08-22  0:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22  0:25 [OE-core][PATCH v4 0/4] Make signed kernel modules stripped Anis Bougrine
2026-08-22  0:25 ` [OE-core][PATCH v4 1/4] kernel.bbclass: re-sign kernel modules after package stripping process Anis Bougrine
2026-08-22  0:25 ` [OE-core][PATCH v4 2/4] package.py: remove stripping and splitting skip for signed kernel modules Anis Bougrine
2026-08-22  0:26 ` [OE-core][PATCH v4 3/4] kernel: centralize kernel module installation path in one variable Anis Bougrine
2026-08-24 18:57   ` Richard Purdie
2026-08-22  0:26 ` Anis Bougrine [this message]
2026-08-22 16:12 ` [OE-core][PATCH v4 0/4] Make signed kernel modules stripped Mathieu Dubois-Briand
2026-08-24  0:03   ` Bougrine Anis
2026-08-25 18:33 ` Peter Kjellerstedt

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=20260822002601.90667-5-anis.bougrine10@gmail.com \
    --to=anis.bougrine10@gmail.com \
    --cc=antonin.godard@bootlin.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=jose.quaresma@oss.qualcomm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox