All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: dixitparmar19@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] kernel-module-split: fix conf file generation when KERNEL_SPLIT_MODULES=0
Date: Mon, 17 Mar 2025 10:24:22 -0400	[thread overview]
Message-ID: <20250317142422.GA20712@localhost> (raw)
In-Reply-To: <4168.1742113007457227336@lists.openembedded.org>

On Sun 2025-03-16 @ 01:16:47 AM, Dixit Parmar via lists.openembedded.org wrote:
> 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?

What data are you expecting to find, and where are you expecting to find
it, that prompted this fix? I assume that in one case there will be
information/files populated in the image's /etc/modprobe.d and in the other
case (the buggy case) that isn't happening? Or is there something else?

Can you provide complete instructions and/or your configuration demonstrating
the problem occurring before your fix, and the problem being solved by your
fix? Simply enabling KERNEL_SPLIT_MODULES by itself won't show anything unless
the user is trying to enable some module(s) too.

I found that I had to go read the bugzilla report to better understand the
issue and potentially how to show it occurring. Keep the reference to the
bugzilla, but ideally the commit message would have all the necessary
information to understand and reproduce the issue.

> 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.

It is customary that quoted text have the start-of-line ">" symbols (the more
symbols, the further back in history the comment) and that replies not have
any start-of-line character, as I'm doing here. Your email program should have
an option to do this automatically.


  parent reply	other threads:[~2025-03-17 14:24 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
2025-03-16  8:25     ` Dixit Parmar
2025-03-17 14:24     ` Trevor Woerner [this message]
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=20250317142422.GA20712@localhost \
    --to=twoerner@gmail.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.