From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Trevor Gamblin <tgamblin@baylibre.com>
Subject: [mickledore][PATCH 2/4] dev-manual: fix testimage usage instructions
Date: Wed, 11 Oct 2023 15:37:18 +0200 [thread overview]
Message-ID: <20231011133720.78265-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231011133720.78265-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Trevor Gamblin <tgamblin@baylibre.com>
The proper way to inherit the testimage class is now
IMAGE_CLASSES += "testimage"
so change lines with 'INHERIT += "testimage"' to match. This makes the
dev-manual consistent with the migration guide, which already specifies
that the old way causes an error.
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/dev-manual/runtime-testing.rst | 4 ++--
documentation/dev-manual/upgrading-recipes.rst | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/documentation/dev-manual/runtime-testing.rst b/documentation/dev-manual/runtime-testing.rst
index c5c5653bef..af3fe2c1dd 100644
--- a/documentation/dev-manual/runtime-testing.rst
+++ b/documentation/dev-manual/runtime-testing.rst
@@ -229,7 +229,7 @@ The final thing you need to do when setting :term:`TEST_TARGET` to
statements in your ``local.conf`` file::
IMAGE_FSTYPES += "tar.gz"
- INHERIT += "testimage"
+ IMAGE_CLASSES += "testimage"
TEST_TARGET = "SystemdbootTarget"
TEST_TARGET_IP = "192.168.2.3"
@@ -335,7 +335,7 @@ You can start the tests automatically or manually:
inherit the :ref:`ref-classes-testimage` class by editing your
``local.conf`` file::
- INHERIT += "testimage"
+ IMAGE_CLASSES += "testimage"
Next, use BitBake to run the tests::
diff --git a/documentation/dev-manual/upgrading-recipes.rst b/documentation/dev-manual/upgrading-recipes.rst
index 13133fddcf..33a7ca39dd 100644
--- a/documentation/dev-manual/upgrading-recipes.rst
+++ b/documentation/dev-manual/upgrading-recipes.rst
@@ -117,7 +117,7 @@ The following steps describe how to set up the AUH utility:
class, which is optional, you need to have the following set in
your ``conf/local.conf`` file::
- INHERIT += "testimage"
+ IMAGE_CLASSES += "testimage"
.. note::
--
2.34.1
next prev parent reply other threads:[~2023-10-11 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 13:37 [mickledore][PATCH 1/4] ref-manual: releases.svg: Scarthgap is now version 5.0 michael.opdenacker
2023-10-11 13:37 ` michael.opdenacker [this message]
2023-10-11 13:37 ` [mickledore][PATCH 3/4] overview: Add note about non-reproducibility side effects michael.opdenacker
2023-10-11 13:37 ` [mickledore][PATCH 4/4] migration-guides: add release notes for 4.0.13 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=20231011133720.78265-2-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=tgamblin@baylibre.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