MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 21:09:03 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

contributor-guide: clarify patchtest usage

Browse Source 
- Make it clear that patchtest only supports openembedded-core for now
- Add a short list of instructions for installing Python module
  dependencies on the host
- Add a step to add meta-selftest with bitbake layers so that all tests
  can run

(From yocto-docs rev: bcd58d68e72226be1930593f5f7fb37de15b7913)

Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Trevor Gamblin 2023-10-17 12:32:03 -04:00 committed by Richard Purdie
parent 544da7651d
commit 884c37f6fd
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
documentation/contributor-guide/submit-changes.rst
View File

@ -282,12 +282,18 @@ Here is the general procedure on how to create patches to be sent through email:
Validating Patches with Patchtest
=================================
``patchtest`` is available in ``openembedded-core`` as a tool for making sure
that your patches are well-formatted and contain important info for
``patchtest`` is available in ``openembedded-core`` as a tool for making
sure that your patches are well-formatted and contain important info for
maintenance purposes, such as ``Signed-off-by`` and ``Upstream-Status``
tags. Once you have generated the patch files and run ``source
oe-init-build-env`` to initialize your workspace, you can run ``patchtest``
like so::
tags. Currently, it only supports testing patches for
``openembedded-core`` branches. To setup, perform the following::
pip install -r meta/lib/patchtest/requirements.txt
source oe-init-build-env
bitbake-layers add-layer ../meta-selftest
Once these steps are complete and you have generated your patch files,
you can run ``patchtest`` like so::
patchtest --patch <patch_name>