rename NET to NET_LEGACY
Highlight that NET really is the legacy networking stack by renaming the option to NET_LEGACY. This requires us to add an SPL_NET_LEGACY alias to SPL_NET as otherwise CONFIG_IS_ENABLED(NET_LEGACY) will not work for SPL. The "depends on !NET_LWIP" for SPL_NET clearly highlights that it is using the legacy networking app so this seems fine to do. This also has the benefit of removing potential confusion on NET being a specific networking stack instead of "any" network stack. Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Acked-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by: Peter Robinson <pbrobinson@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
@@ -546,11 +546,11 @@ following annotation for a test requires ``CONFIG_EFI_LOADER=y``:
|
||||
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:
|
||||
either of ``CONFIG_NET_LEGACY`` or ``CONFIG_NET_LWIP`` is set:
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
@pytest.mark.buildconfigspec('net', 'net_lwip')
|
||||
@pytest.mark.buildconfigspec('net_legacy', 'net_lwip')
|
||||
|
||||
The ``notbuildconfigspec()`` annotation can be used to require a configuration
|
||||
option not to be set. The following annotation requires ``CONFIG_RISCV=n``:
|
||||
|
||||
Reference in New Issue
Block a user