Commit 383f1a8d authored by Daniel Müller's avatar Daniel Müller Committed by Daniel Borkmann

bpf/docs: Include blank lines between bullet points in bpf_devel_QA.rst

Commit 26a9b433 ("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: 26a9b433 ("bpf/docs: Document how to run CI without patch submission")
Reported-by: default avatarAkira Yokosawa <akiyks@gmail.com>
Signed-off-by: default avatarDaniel Müller <deso@posteo.net>
Signed-off-by: default avatarDaniel Borkmann <daniel@iogearbox.net>
Reviewed-by: default avatarAkira Yokosawa <akiyks@gmail.com>
Link: https://lore.kernel.org/bpf/20221116174358.2744613-1-deso@posteo.net
parent c453e64c
...@@ -51,10 +51,13 @@ While GitHub also provides a CLI that can be used to accomplish the same ...@@ -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. results, here we focus on the UI based workflow.
The following steps lay out how to start a CI run for your patches: 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 - Create a fork of the aforementioned repository in your own account (one time
action) action)
- Clone the fork locally, check out a new branch tracking either the bpf-next - 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 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 - 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 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
......
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