diff options
| author | Daniel Müller <deso@posteo.net> | 2022-11-16 17:43:58 +0000 |
|---|---|---|
| committer | Daniel Borkmann <daniel@iogearbox.net> | 2022-11-17 16:26:42 +0100 |
| commit | 383f1a8df8faba88a3bafaddc02f59421bad6829 (patch) | |
| tree | 5a885005128834cef239b604d679d496d9712705 /Documentation/bpf | |
| parent | c453e64cbc9532c0c2edfa999c35d29dad16b8bb (diff) | |
| download | linux-383f1a8df8faba88a3bafaddc02f59421bad6829.tar.gz | |
bpf/docs: Include blank lines between bullet points in bpf_devel_QA.rst
Commit 26a9b433cf08 ("bpf/docs: Document how to run CI without patch
submission") caused a warning to be generated when compiling the
documentation:
> bpf_devel_QA.rst:55: WARNING: Unexpected indentation.
> bpf_devel_QA.rst:56: WARNING: Block quote ends without a blank line
This change fixes the problem by inserting the required blank lines.
Fixes: 26a9b433cf08 ("bpf/docs: Document how to run CI without patch submission")
Reported-by: Akira Yokosawa <akiyks@gmail.com>
Signed-off-by: Daniel Müller <deso@posteo.net>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
Link: https://lore.kernel.org/bpf/20221116174358.2744613-1-deso@posteo.net
Diffstat (limited to 'Documentation/bpf')
| -rw-r--r-- | Documentation/bpf/bpf_devel_QA.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst index 08572c75bdef39..03d4993eda6f05 100644 --- a/Documentation/bpf/bpf_devel_QA.rst +++ b/Documentation/bpf/bpf_devel_QA.rst @@ -51,10 +51,13 @@ While GitHub also provides a CLI that can be used to accomplish the same results, here we focus on the UI based workflow. The following steps lay out how to start a CI run for your patches: + - Create a fork of the aforementioned repository in your own account (one time action) + - Clone the fork locally, check out a new branch tracking either the bpf-next or bpf branch, and apply your to-be-tested patches on top of it + - Push the local branch to your fork and create a pull request against kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively |