diff options
author | Jakub Kicinski <[email protected]> | 2023-07-19 11:32:25 -0700 |
---|---|---|
committer | Jonathan Corbet <[email protected]> | 2023-07-21 13:47:10 -0600 |
commit | 4454d38261ac7def5fe97d5a29cad6899f1dde53 (patch) | |
tree | f6f76996caf0e06f25d9d6802a8659f1a4490f6b /tools/testing/selftests/bpf/prog_tests/autoload.c | |
parent | 626c820526a0b1c1801612f4bfd2f6b6163373fc (diff) |
docs: maintainer: document expectations of small time maintainers
We appear to have a gap in our process docs. We go into detail
on how to contribute code to the kernel, and how to be a subsystem
maintainer. I can't find any docs directed towards the thousands
of small scale maintainers, like folks maintaining a single driver
or a single network protocol.
Document our expectations and best practices. I'm hoping this doc
will be particularly useful to set expectations with HW vendors.
Reviewed-by: Andrew Lunn <[email protected]>
Reviewed-by: Greg Kroah-Hartman <[email protected]>
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Reviewed-by: Mark Brown <[email protected]>
Reviewed-by: Leon Romanovsky <[email protected]>
Signed-off-by: Jakub Kicinski <[email protected]>
Reviewed-by: Simon Horman <[email protected]>
Reviewed-by: Martin Habets <[email protected]>
Reviewed-by: Conor Dooley <[email protected]>
Signed-off-by: Jonathan Corbet <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions