From: Jon Mason <jdmason@kudzu.us>
To: Peter Hoyes <peter.hoyes@arm.com>
Cc: yocto@lists.yoctoproject.org, diego.sueiro@arm.com
Subject: Re: [meta-zephyr][PATCH 0/4] Add script for version upgrades
Date: Tue, 20 Sep 2022 18:33:44 -0400 [thread overview]
Message-ID: <Yyo/yOgwvrsoxGPf@kudzu.us> (raw)
In-Reply-To: <20220916090318.1293922-1-peter.hoyes@arm.com>
On Fri, Sep 16, 2022 at 10:03:14AM +0100, Peter Hoyes wrote:
> From: Peter Hoyes <Peter.Hoyes@arm.com>
>
> This patch chain has been developed on top of the 2.7.3 upgrade patch.
>
> Add a script, generate-version.py, which can be used to automatically
> generate configuration for new Zephyr versions. Regenerate
> configuration for 2.7.3 and 3.1.0 using this script.
>
> This script includes a constant version-specific declaration of
> ZEPHYR_MODULES, so the build-time logic to extract ZEPHYR_MODULES is no
> longer required. Remove the do_get_zmods task and the West recipe.
>
> Peter Hoyes (4):
> zephyr-core/scripts: Introduce script to generate new versions
> zephyr-core/zephyr-kernel: Migrate to script-driven version files
> zephyr-core/classes: Remove West-based logic from zephyr.bbclass
> zephyr-core/zephyr-kernel: Update dtc.patch Upstream-Status
Series passes CI (on top of the v2.7.3 patch). See
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/645914527
Tested-by: Jon Mason <jon.mason@arm.com>
>
> README.txt | 17 ++
> meta-zephyr-core/classes/zephyr.bbclass | 32 +--
> .../recipes-devtools/west/west_0.12.99.bb | 22 --
> ...y-generation-issue-in-cross-compila.patch} | 0
> .../zephyr-kernel/files/dtc.patch | 2 +-
> .../zephyr-kernel/zephyr-kernel-src-2.7.3.inc | 202 +++++++++++++---
> .../zephyr-kernel/zephyr-kernel-src-3.1.0.inc | 220 +++++++++++++++---
> .../zephyr-kernel/zephyr-kernel-src.inc | 43 ----
> meta-zephyr-core/scripts/generate-version.py | 73 ++++++
> .../scripts/zephyr-kernel-src.inc.jinja | 35 +++
> 10 files changed, 474 insertions(+), 172 deletions(-)
> delete mode 100644 meta-zephyr-core/recipes-devtools/west/west_0.12.99.bb
> rename meta-zephyr-core/recipes-kernel/zephyr-kernel/files/{0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch => 0001-2.7-x86-fix-efi-binary-generation-issue-in-cross-compila.patch} (100%)
> create mode 100755 meta-zephyr-core/scripts/generate-version.py
> create mode 100644 meta-zephyr-core/scripts/zephyr-kernel-src.inc.jinja
>
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2022-09-20 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 9:03 [meta-zephyr][PATCH 0/4] Add script for version upgrades Peter Hoyes
2022-09-16 9:03 ` [meta-zephyr][PATCH 1/4] zephyr-core/scripts: Introduce script to generate new versions Peter Hoyes
2022-09-16 9:03 ` [meta-zephyr][PATCH 2/4] zephyr-core/zephyr-kernel: Migrate to script-driven version files Peter Hoyes
2022-09-16 9:03 ` [meta-zephyr][PATCH 3/4] zephyr-core/classes: Remove West-based logic from zephyr.bbclass Peter Hoyes
2022-09-16 9:03 ` [meta-zephyr][PATCH 4/4] zephyr-core/zephyr-kernel: Update dtc.patch Upstream-Status Peter Hoyes
2022-09-20 22:33 ` Jon Mason [this message]
2022-09-21 8:49 ` [yocto] [meta-zephyr][PATCH 0/4] Add script for version upgrades Saini, Naveen Kumar
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=Yyo/yOgwvrsoxGPf@kudzu.us \
--to=jdmason@kudzu.us \
--cc=diego.sueiro@arm.com \
--cc=peter.hoyes@arm.com \
--cc=yocto@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox