bpf/docs: Document how to run CI without patch submission
authorDaniel Müller <deso@posteo.net>
Mon, 14 Nov 2022 21:15:01 +0000 (21:15 +0000)
committerDaniel Borkmann <daniel@iogearbox.net>
Tue, 15 Nov 2022 14:33:27 +0000 (15:33 +0100)
commit26a9b433cf08adf2fdb50775128b283eb5201ab2
tree2a30635d31c437442af07ad1f37ac72b4faeaff3
parent6728aea7216c0c06c98e2e58d753a5e8b2ae1c6f
bpf/docs: Document how to run CI without patch submission

This change documents the process for running the BPF CI before
submitting a patch to the upstream mailing list, similar to what happens
if a patch is send to bpf@vger.kernel.org: it builds kernel and
selftests and runs the latter on different architecture (but it notably
does not cover stylistic checks such as cover letter verification).

Running BPF CI this way can help achieve better test coverage ahead of
patch submission than merely running locally (say, using
tools/testing/selftests/bpf/vmtest.sh), as additional architectures may
be covered as well.

Signed-off-by: Daniel Müller <deso@posteo.net>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/bpf/20221114211501.2068684-1-deso@posteo.net
Documentation/bpf/bpf_devel_QA.rst