Commit 3eca3814 authored by Jakub Kicinski's avatar Jakub Kicinski Committed by Paolo Abeni

docs: netdev: make the testing requirement more stringent

These days we often ask for selftests so let's update our
testing requirements.
Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
Reviewed-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
Signed-off-by: default avatarPaolo Abeni <pabeni@redhat.com>
parent b8ba1063
...@@ -196,11 +196,15 @@ as possible alternative mechanisms. ...@@ -196,11 +196,15 @@ as possible alternative mechanisms.
What level of testing is expected before I submit my change? What level of testing is expected before I submit my change?
------------------------------------------------------------ ------------------------------------------------------------
If your changes are against ``net-next``, the expectation is that you At the very minimum your changes must survive an ``allyesconfig`` and an
have tested by layering your changes on top of ``net-next``. Ideally ``allmodconfig`` build with ``W=1`` set without new warnings or failures.
you will have done run-time testing specific to your change, but at a
minimum, your changes should survive an ``allyesconfig`` and an Ideally you will have done run-time testing specific to your change,
``allmodconfig`` build without new warnings or failures. and the patch series contains a set of kernel selftest for
``tools/testing/selftests/net`` or using the KUnit framework.
You are expected to test your changes on top of the relevant networking
tree (``net`` or ``net-next``) and not e.g. a stable tree or ``linux-next``.
How do I post corresponding changes to user space components? How do I post corresponding changes to user space components?
------------------------------------------------------------- -------------------------------------------------------------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment