diff options
author | Tom Rini <trini@konsulko.com> | 2025-05-26 16:07:19 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2025-05-26 16:07:19 -0600 |
commit | 39b815d02d7ce6af32bcf023d20243c404b75a84 (patch) | |
tree | 68cd13fa83e90f69bf8c989fbcde768b676eb6d7 /doc/develop | |
parent | bab54f5942c428be698216224fd10b91d974d4da (diff) | |
parent | 2ca1398a5ece8d33d8feb6b410e6e38588b5d2bc (diff) |
Merge tag 'v2025.07-rc3' into next
Prepare v2025.07-rc3
Diffstat (limited to 'doc/develop')
-rw-r--r-- | doc/develop/cyclic.rst | 13 | ||||
-rw-r--r-- | doc/develop/pytest/index.rst | 10 | ||||
-rw-r--r-- | doc/develop/pytest/usage.rst | 24 | ||||
-rw-r--r-- | doc/develop/release_cycle.rst | 2 |
4 files changed, 40 insertions, 9 deletions
diff --git a/doc/develop/cyclic.rst b/doc/develop/cyclic.rst index 6f1da6f0d9b..a99b17052f5 100644 --- a/doc/develop/cyclic.rst +++ b/doc/develop/cyclic.rst @@ -54,3 +54,16 @@ responsible for calling all registered cyclic functions, into the common schedule() function. This guarantees that cyclic_run() is executed very often, which is necessary for the cyclic functions to get scheduled and executed at their configured periods. + +Idempotence +----------- + +Both the cyclic_register() and cyclic_unregister() functions are safe +to call on any struct cyclic_info, regardless of whether that instance +is already registered or not. + +More specifically, calling cyclic_unregister() with a cyclic_info +which is not currently registered is a no-op, while calling +cyclic_register() with a cyclic_info which is currently registered +results in it being automatically unregistered, and then registered +with the new callback function and timeout parameters. diff --git a/doc/develop/pytest/index.rst b/doc/develop/pytest/index.rst index 0a7c1b21a24..dce8a96370f 100644 --- a/doc/develop/pytest/index.rst +++ b/doc/develop/pytest/index.rst @@ -16,12 +16,6 @@ Individual tests .. toctree:: :maxdepth: 1 + :glob: - test_000_version - test_bind - test_bootmenu - test_bootstage - test_button - test_efi_loader - test_net - test_net_boot + test_* diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst index 49d269d66a7..779b2dbe24b 100644 --- a/doc/develop/pytest/usage.rst +++ b/doc/develop/pytest/usage.rst @@ -522,3 +522,27 @@ of the `ubman.config` object, for example Build configuration values (from `.config`) may be accessed via the dictionary `ubman.config.buildconfig`, with keys equal to the Kconfig variable names. + +A required configuration setting can be defined via a buildconfigspec() +annotation. The name of the configuration option is specified in lower case. The +following annotation for a test requires CONFIG_EFI_LOADER=y: + +.. code-block:: python + + @pytest.mark.buildconfigspec('efi_loader') + +Sometimes multiple configuration option supply the same functionality. If +multiple arguments are passed to buildconfigspec(), only one of the +configuration options needs to be set. The following annotation requires that +either of CONFIG_NET or CONFIG_NET_LWIP is set: + +.. code-block:: python + + @pytest.mark.buildconfigspec('net', 'net lwip') + +The notbuildconfigspec() annotation can be used to require a configuration +option not to be set. The following annotation requires CONFIG_RISCV=n: + +.. code-block:: python + + @pytest.mark.notbuildconfigspec('riscv') diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst index b68b462257d..36bb9055e6a 100644 --- a/doc/develop/release_cycle.rst +++ b/doc/develop/release_cycle.rst @@ -75,7 +75,7 @@ For the next scheduled release, release candidates were made on:: * U-Boot |next_ver|-rc2 was released on Mon 12 May 2025. -.. * U-Boot |next_ver|-rc3 was released on Mon 26 May 2025. +* U-Boot |next_ver|-rc3 was released on Mon 26 May 2025. .. * U-Boot |next_ver|-rc4 was released on Mon 09 June 2025. |