From patchwork Wed Nov 16 17:43:58 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Daniel_M=C3=BCller?= X-Patchwork-Id: 13045610 X-Patchwork-Delegate: bpf@iogearbox.net Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 88B9FC4332F for ; Wed, 16 Nov 2022 17:44:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229617AbiKPRoW (ORCPT ); Wed, 16 Nov 2022 12:44:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238829AbiKPRoM (ORCPT ); Wed, 16 Nov 2022 12:44:12 -0500 Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7E657E019 for ; Wed, 16 Nov 2022 09:44:11 -0800 (PST) Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 0242524002C for ; Wed, 16 Nov 2022 18:44:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668620650; bh=AH/hAIBswvARWgzvBJE3iV9aPdnnP096ae0gtREDiwk=; h=From:To:Cc:Subject:Date:From; b=jyCB/8lKBMQEZ5T4sHrQfFfQil8myanRc4maFECjT5VATFKycpggHGNbQJ5ue/ZD4 dg/rziJ6w3C8dsgJvkUBovqI+O/ajN47bWTIFA/5E0X5klgFTh1jbdj5j0eTrgnw5K 7/U0NI3j2UHulxu9kwe7jq2yybQ9ZkzMPiKZELXWvnXBUNN51JbQ8D5ngKUEBwARNS Gxogcyh6dxKi7qkp0bqev8PDHHitfBNZ34Hcd5L4cuC1mnpLWsCjBd8tIiqYkBFZc5 aTTxIyky/udRy24PEyDbUBaiaaddcGYtk/OMCIwyPMBswqnZZzUvEyTYZ3j3xxtQTe YgtFkJUuIC4Mw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NC9Qc2ppsz9rxL; Wed, 16 Nov 2022 18:44:08 +0100 (CET) From: =?utf-8?q?Daniel_M=C3=BCller?= To: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net, kafai@fb.com, kernel-team@fb.com Cc: deso@posteo.net, Akira Yokosawa Subject: [PATCH bpf-next] bpf/docs: Include blank lines between bullet points in bpf_devel_QA.rst Date: Wed, 16 Nov 2022 17:43:58 +0000 Message-Id: <20221116174358.2744613-1-deso@posteo.net> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org X-Patchwork-Delegate: bpf@iogearbox.net 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 Signed-off-by: Daniel Müller Reviewed-by: Akira Yokosawa --- Documentation/bpf/bpf_devel_QA.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst index 08572c7..03d499 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