All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Pittman <bill.pittman@ni.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: [OE-core] [PATCH] wic: Use custom kernel path if provided
Date: Mon, 7 Mar 2022 16:38:29 +0000	[thread overview]
Message-ID: <SN6PR04MB490954026B270D62EBDA29F5EC089@SN6PR04MB4909.namprd04.prod.outlook.com> (raw)
In-Reply-To: <SN6PR04MB4909394161091073345E1ACBEC089@SN6PR04MB4909.namprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

Richard,

I don't think there are any additional test cases that need to be created for this condition.  It is a fairly unique set of circumstances that cause an error in our build system and would be difficult to reproduce outside of it.

As for your concern about this being the right thing to do, honestly I'm not sure, but it does seem wrong to me that there is a code path that ignores the value in options.kernel_dir, which is why I proposed the patch (and of course our build system was being affected by it).  I'm not sure if it is right or not, but it seems "more right" to me.

Hope that helps,
Bill


________________________________
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Sent: Wednesday, March 2, 2022 5:02 PM
To: Bill Pittman <bill.pittman@ni.com>; openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org>
Subject: [EXTERNAL] Re: [OE-core] [PATCH] wic: Use custom kernel path if provided

On Tue, 2022-02-15 at 16:54 +0000, Bill Pittman wrote:
> If the custom kernel path is provided in options, then
> use that path instead of the default path.
>
> Signed-off-by: Bill Pittman <bill.pittman@ni.com>
> ---
>  scripts/wic | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/scripts/wic b/scripts/wic
> index a741aed364..29a157bf37 100755
> --- a/scripts/wic
> +++ b/scripts/wic
> @@ -159,6 +159,9 @@ def wic_create_subcommand(options, usage_str):
>                             "(Use -e/--image-name to specify it)")
>          native_sysroot = options.native_sysroot
>
> +    if options.kernel_dir:
> +        kernel_dir = options.kernel_dir
> +
>      if not options.vars_dir and (not native_sysroot or not
> os.path.isdir(native_sysroot)):
>          logger.info("Building wic-tools...\n")
>          subprocess.check_call(["bitbake", "wic-tools"])


The concern with these kinds of changes is I can't really test it or tell if it
is the right thing to do and I worry about it regressing in the future.

Is there part of the test coverage we should be improving too? wic does have
fairly good coverage from oe-selftest -r wic

Cheers,

Richard



INTERNAL - NI CONFIDENTIAL

[-- Attachment #2: Type: text/html, Size: 4274 bytes --]

      parent reply	other threads:[~2022-03-07 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 16:54 [PATCH] wic: Use custom kernel path if provided Bill Pittman
2022-03-02 18:15 ` Bill Pittman
2022-03-02 22:06 ` [OE-core] " Andrei Gherzan
     [not found]   ` <SN6PR04MB49098B84F7D5490D734B7EB1EC089@SN6PR04MB4909.namprd04.prod.outlook.com>
2022-03-07 16:37     ` Bill Pittman
2022-03-02 23:02 ` [OE-core] " Richard Purdie
     [not found]   ` <SN6PR04MB4909394161091073345E1ACBEC089@SN6PR04MB4909.namprd04.prod.outlook.com>
2022-03-07 16:38     ` Bill Pittman [this message]

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=SN6PR04MB490954026B270D62EBDA29F5EC089@SN6PR04MB4909.namprd04.prod.outlook.com \
    --to=bill.pittman@ni.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.