diff options
| author | Trevor Woerner <twoerner@gmail.com> | 2025-09-18 17:27:25 -0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-09-22 22:09:48 +0100 |
| commit | cd493181d70e55a0c67535c5bd9661e224ef7237 (patch) | |
| tree | 196f0c757ab57f7c914ac9be8aed889e980c8d68 | |
| parent | 45c7810b4ff337ba578cbda2d86ae33d73caee90 (diff) | |
| download | poky-cd493181d70e55a0c67535c5bd9661e224ef7237.tar.gz | |
patchtest.README: update name and location or patchtest layer
The patchtest layer's name and location have changed from:
patchtest
https://git.yoctoproject.org/patchtest
to:
meta-patchtest
https://git.yoctoproject.org/meta-patchtest
Update any references of the old name and repository to the new ones.
(From OE-Core rev: 166e52103d17c9eeec3666967c2580008f992481)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | scripts/patchtest.README | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/scripts/patchtest.README b/scripts/patchtest.README index 1c674e23c9..5a9dabc50b 100644 --- a/scripts/patchtest.README +++ b/scripts/patchtest.README | |||
| @@ -20,8 +20,9 @@ which environment you prefer. If you plan to test your own patches (a | |||
| 20 | good practice before these are sent to the mailing list), the easiest | 20 | good practice before these are sent to the mailing list), the easiest |
| 21 | way is to install and execute on your local host; on the other hand, if | 21 | way is to install and execute on your local host; on the other hand, if |
| 22 | automatic testing is intended, the guest method is strongly recommended. | 22 | automatic testing is intended, the guest method is strongly recommended. |
| 23 | The guest method requires the use of the patchtest layer, in addition to | 23 | The guest method requires the use of the meta-patchtest layer, in |
| 24 | the tools available in oe-core: https://git.yoctoproject.org/patchtest/ | 24 | addition to the tools available in oe-core: |
| 25 | https://git.yoctoproject.org/meta-patchtest/ | ||
| 25 | 26 | ||
| 26 | ## Installation | 27 | ## Installation |
| 27 | 28 | ||
| @@ -43,7 +44,7 @@ To work with patchtest, you should have the following repositories cloned: | |||
| 43 | 44 | ||
| 44 | 1. https://git.openembedded.org/openembedded-core/ (or https://git.yoctoproject.org/poky/) | 45 | 1. https://git.openembedded.org/openembedded-core/ (or https://git.yoctoproject.org/poky/) |
| 45 | 2. https://git.openembedded.org/bitbake/ (if not using poky) | 46 | 2. https://git.openembedded.org/bitbake/ (if not using poky) |
| 46 | 3. https://git.yoctoproject.org/patchtest (if using guest mode) | 47 | 3. https://git.yoctoproject.org/meta-patchtest (if using guest mode) |
| 47 | 48 | ||
| 48 | ## Usage | 49 | ## Usage |
| 49 | 50 | ||
| @@ -98,8 +99,8 @@ from the mailing lists. When executed this way, the test process is | |||
| 98 | essentially running random code from the internet and could be | 99 | essentially running random code from the internet and could be |
| 99 | catastrophic if malicious bits or even poorly-handled edge cases aren't | 100 | catastrophic if malicious bits or even poorly-handled edge cases aren't |
| 100 | protected against. In order to use this mode, the | 101 | protected against. In order to use this mode, the |
| 101 | https://git.yoctoproject.org/patchtest/ repository must be cloned and | 102 | https://git.yoctoproject.org/meta-patchtest/ repository must be cloned |
| 102 | the meta-patchtest layer added to bblayers.conf. | 103 | and added to bblayers.conf. |
| 103 | 104 | ||
| 104 | The general flow of guest mode is: | 105 | The general flow of guest mode is: |
| 105 | 106 | ||