From: "Dixit Parmar" <dixitparmar19@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel-module-split: fix conf file generation when KERNEL_SPLIT_MODULES=0
Date: Sun, 16 Mar 2025 01:16:47 -0700 [thread overview]
Message-ID: <4168.1742113007457227336@lists.openembedded.org> (raw)
In-Reply-To: <Z8IIVTwVir8JCsxE@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
Can you show the conf files for the same kernel configuration
with and without the kernel_split_modules enabled ? That way
we know there's no change in existing behaviour.
> I have confirmed that in my testing. Can you suggest how I can
share that information here?
We also should make a test for this in the OE selftests. We
are adding conditional code paths, so they should be tested
to ensure no regressions in either in the future.
> Never done that before. May be I can do it given some direction
as separate patch.
I'm curious about the above line. It is unclear to me why we'd
only have this postinst be relevant if none was previously set.
> Reverted.
Is there really a scenario where the directory won't exist ? Isn't
this just running in our own install phase ? So all prerequisites
and directories should be in place.
> Ideally no, we kept it for safer side, I have added log warning.
The walking and sorting seems quite heavy. Isn't this called from do_split_packages indirectly ?
Do we really need to walk and gather the information ? Is this mainly for the case of no-split
on the kernel modules ? If that is the case, isn't there a way to short circuit the processing
on the split-package case ?
> Litterally I could not think of anything else here and not sure of there
are any short-circuit options. I have limited knowledge in this. I am open to suggestions
if this is not the best solution at the moment.
[-- Attachment #2: Type: text/html, Size: 1621 bytes --]
next prev parent reply other threads:[~2025-03-16 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 7:11 [PATCH] kernel-module-split: fix conf file generation when KERNEL_SPLIT_MODULES=0 Dixit Parmar
2025-02-28 19:02 ` [OE-core] " Bruce Ashfield
2025-03-16 8:16 ` Dixit Parmar [this message]
2025-03-16 8:25 ` Dixit Parmar
2025-03-17 14:24 ` [OE-core] " Trevor Woerner
2025-03-19 7:40 ` Dixit Parmar
2025-03-19 13:00 ` [OE-core] " Bruce Ashfield
2025-03-16 8:21 ` [PATCH 1/1] " Dixit Parmar
2025-03-20 19:22 ` [OE-core] " Bruce Ashfield
2025-03-21 6:57 ` Dixit Parmar
2025-03-16 8:22 ` [PATCH V2] " 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=4168.1742113007457227336@lists.openembedded.org \
--to=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.