From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: michael.opdenacker@bootlin.com, openembedded-core@lists.openembedded.org
Cc: Frederic Martinsons <frederic.martinsons@gmail.com>,
Marta Rybczynska <rybczynska@gmail.com>,
Paul Eggleton <paul.eggleton@linux.microsoft.com>,
Alex Kiernan <alex.kiernan@gmail.com>
Subject: Re: [OE-core] [PATCH v2] migration-guides: update 4.2 migration and release notes
Date: Thu, 06 Apr 2023 11:12:47 +0100 [thread overview]
Message-ID: <927715c9e53832471789990ddccaba4cfc77c3ca.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230406091254.248215-1-michael.opdenacker@bootlin.com>
On Thu, 2023-04-06 at 11:12 +0200, Michael Opdenacker via
lists.openembedded.org wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> CC: Frederic Martinsons <frederic.martinsons@gmail.com>
> CC: Marta Rybczynska <rybczynska@gmail.com>
> CC: Paul Eggleton <paul.eggleton@linux.microsoft.com>
> CC: Alex Kiernan <alex.kiernan@gmail.com>
>
> ---
>
> Changes in V2:
> - Add details about filling checksums using the 'cargo-update-recipe-crates'
> class, as suggested by Frederic Martinsons.
We should add something about ptest changes:
"""
The ptest images have changed structure in this release. The underlying
core-image-ptest recipe now uses BBCLASSEXTEND to create a variant for
each ptest enabled recipe in OE-Core.
For example, this means that "core-image-ptest-bzip2", "core-image-
ptest-lttng-tools" and many more image targets now exist and can be
built/tested individually.
The core-image-ptest-all and core-image-ptest-fast targets are now
wrappers that target groups of individual images and means that the
tests can be executed in parallel during our automated testing. This
also means the dependencies are more accurately tested.
"""
Cheers,
Richard
next prev parent reply other threads:[~2023-04-06 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17531B0D0DFA1CB6.3977@lists.openembedded.org>
2023-04-05 18:40 ` [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes Michael Opdenacker
2023-04-05 19:04 ` Frédéric Martinsons
2023-04-06 8:23 ` [docs] " Michael Opdenacker
2023-04-06 8:52 ` Frédéric Martinsons
2023-04-06 9:12 ` [PATCH v2] " michael.opdenacker
2023-04-06 10:12 ` Richard Purdie [this message]
2023-04-06 20:53 ` [OE-core] " Michael Opdenacker
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=927715c9e53832471789990ddccaba4cfc77c3ca.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kiernan@gmail.com \
--cc=frederic.martinsons@gmail.com \
--cc=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.microsoft.com \
--cc=rybczynska@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox