All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <dixitparmar19@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/1] kernel-module-split: fix conf file generation when KERNEL_SPLIT_MODULES=0
Date: Fri, 06 Jun 2025 10:02:04 +0200	[thread overview]
Message-ID: <DAFAK5RG00NC.29AFZ7K01KRC@bootlin.com> (raw)
In-Reply-To: <20250605131235.366013-1-dixitparmar19@gmail.com>

On Thu Jun 5, 2025 at 3:12 PM CEST, Dixit Parmar via lists.openembedded.org wrote:
> KERNEL_MODULE_AUTOLOAD defines the list of the kernel modules to be autoloaded
> on boot. kernel-module-split.bbclass generates the required modules.load.d and
> conf files for each kernel module. This conf files inturn read by system service
> to perform module loading and configuration. When a kernel module is added to
> KERNEL_MODULE_AUTOLOAD the conf files must be generated in all cases.
> When KERNEL_SPLIT_MODULES=0 modprobe and autoload conf files are not
> getting generated for the kernel modules.
> To fix that enhanced the class implementation by separating out conf
> file handling mechanism in two functions, generate_conf_files() and
> frob_metadata(). generate_conf_files() handles no-split case where as
> frob_metadata() keeps handling the existing case for spliting the modules.
> Splitted common handling/generation of conf files stuff in to handle_conf_files()
> function which gets invoked by both frob_metadata() and generate_conf_files()
> on top of the scenario specific handling done in respective functions.
> This implementation covers generation of the conf files for in-tree kernel
> modules as well as standalone kernel module built as seperate package/recipe.
>
> [YOCTO #15145]
>
> Signed-off-by: Dixit Parmar <dixitparmar19@gmail.com>
>
> ---

Hi Dixit,

I have some conflicts while trying to apply this on master branch. Do
you confirm this is targeting master?

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 13:12 [PATCH 1/1] kernel-module-split: fix conf file generation when KERNEL_SPLIT_MODULES=0 Dixit Parmar
2025-06-05 13:16 ` [OE-core] " Bruce Ashfield
2025-06-06  8:02 ` Mathieu Dubois-Briand [this message]
2025-06-07 10:28   ` Dixit Parmar
  -- strict thread matches above, loose matches on Subject: below --
2025-02-22  7:11 [PATCH] " Dixit Parmar
2025-03-16  8:21 ` [PATCH 1/1] " Dixit Parmar
2025-03-20 19:22   ` [OE-core] " Bruce Ashfield

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=DAFAK5RG00NC.29AFZ7K01KRC@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=dixitparmar19@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.