diff options
| author | Jakub Kicinski <[email protected]> | 2023-01-26 16:28:50 -0800 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2023-01-26 16:28:51 -0800 |
| commit | 868c82f34cab6d3ac9e25e355a1c3c5fcb84ec2b (patch) | |
| tree | 0350c030656f998cac9684d579b3f4f580eff2a6 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | 9179f5fe41733ff56f7dfcb83c0c1456f6d2e4ae (diff) | |
| parent | 8c284ea429d2dc6da76c30af281c292d3d428614 (diff) | |
Merge branch 'convert-drivers-to-return-xfrm-configuration-errors-through-extack'
Leon Romanovsky says:
====================
Convert drivers to return XFRM configuration errors through extack
This series continues effort started by Sabrina to return XFRM configuration
errors through extack. It allows for user space software stack easily present
driver failure reasons to users.
As a note, Intel drivers have a path where extack is equal to NULL, and error
prints won't be available in current patchset. If it is needed, it can be
changed by adding special to Intel macro to print to dmesg in case of
extack == NULL.
====================
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions