From: Denys Dmytriyenko <denys@ti.com>
To: Paul Barker <pbarker@konsulko.com>
Cc: meta-arago@arago-project.org
Subject: Re: [master/dunfell][PATCH] linux: copy-defconfig: Move do_create_srcipk only if defined
Date: Mon, 29 Jun 2020 18:43:51 -0400 [thread overview]
Message-ID: <20200629224351.GD6525@beryl> (raw)
In-Reply-To: <20200621204349.363584-1-pbarker@konsulko.com>
Thanks, will merge it shortly.
On Sun, Jun 21, 2020 at 09:43:49PM +0100, Paul Barker wrote:
> Signed-off-by: Paul Barker <pbarker@konsulko.com>
> ---
> .../recipes-kernel/linux/copy-defconfig.inc | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/meta-arago-distro/recipes-kernel/linux/copy-defconfig.inc b/meta-arago-distro/recipes-kernel/linux/copy-defconfig.inc
> index 10ecf8ea..65b615cb 100644
> --- a/meta-arago-distro/recipes-kernel/linux/copy-defconfig.inc
> +++ b/meta-arago-distro/recipes-kernel/linux/copy-defconfig.inc
> @@ -17,6 +17,9 @@ do_configure_append() {
> fi
> }
>
> -# Move create_srcipk task so that the release defconfig is included.
> -deltask do_create_srcipk
> -addtask create_srcipk after do_configure before do_compile
> +python __anonymous() {
> + # Move create_srcipk task so that the release defconfig is included.
> + if d.getVarFlag('do_create_srcipk', "task"):
> + bb.build.deltask('do_create_srcipk', d)
> + bb.build.addtask('do_create_srcipk', 'do_configure', 'do_compile', d)
> +}
> --
> 2.27.0
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
next prev parent reply other threads:[~2020-06-29 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:43 [master/dunfell][PATCH] linux: copy-defconfig: Move do_create_srcipk only if defined Paul Barker
2020-06-29 22:43 ` Denys Dmytriyenko [this message]
2020-06-30 21:30 ` Denys Dmytriyenko
2020-08-14 22:30 ` Denys Dmytriyenko
2020-10-19 19:12 ` Paul Barker
2020-10-19 19:56 ` Denys Dmytriyenko
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=20200629224351.GD6525@beryl \
--to=denys@ti.com \
--cc=meta-arago@arago-project.org \
--cc=pbarker@konsulko.com \
/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.