Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp118477pxy; Wed, 21 Apr 2021 20:38:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxb39RHSZLC4wDYXD8BoUUuY2JTsfMhLH5uAQ3oNbVYSGoOmbWzS+6AwiOrvcI4FUNYvwPq X-Received: by 2002:a05:6402:350f:: with SMTP id b15mr1229061edd.6.1619062704362; Wed, 21 Apr 2021 20:38:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619062704; cv=none; d=google.com; s=arc-20160816; b=WBAgtzDz6Uwb9yQ1Oc8kx8haCH+iEAQDlvYeb17kSgecvzk9XVvW/vu8U5tptUVGch l6BP8UOEFfEU/UpmVESVC51CUYixy4Ijsqg2lc/yYA4Ky1uTq9MyHGraU4PkH+QvgGXv gsBv5JI9imXxVNwLmVr9AjTXfRIOnyCo1bIRZ2aqKKDaL7C+Q9Lv8R65fq5iZYxPTBQM inE/0yeWd9qjZu3jbmyFoKarBFSmk0QFaqCvHRMkMMBNEQsIcUb7uyIx/dD4LInODRG+ XhgcY4mBAnNZ5j5dkT8TkWvOSIhzLezbZsmtm9GpJR1kgv33St6eFGO32tCH6wtMDr1i lsHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from; bh=Pct4liksFiPJoKNbh+QLzSV06PO/R/+Fj2M2xGxSti0=; b=jEu3Nqq85ldvTW26GVMPKr8/fhKRNJ910tYpbIiIzRlSXkfYkJ7Mf+T7Ag7O3Kc2yo 2LbhINLHBXx6Xz4osd5W88/lDdeM9vWqrspOygcYpSTmAV3YfWzJ6OLTmnN98JZ8em+Y Pt/rXK4IQToXW7buiG4tenic5CFjYhOnPRk5ZodvIqGK7/s39thH0hDV9sC6lA3HKw2R rNx1YaYG3yGQNpDUon4guaTSJH0AgtQZYEIZ/I5SOMnn4pNk7PwmXzVZTOYGPrEBDN/1 c4iofw3LAgEoYIBvgYMkCdsOP/b/LscnFq3genqBZdXey5GYBU1vN1v+ajnUhkEjWwbg SIPA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bd8si1022870edb.453.2021.04.21.20.38.01; Wed, 21 Apr 2021 20:38:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234777AbhDVDgy (ORCPT + 99 others); Wed, 21 Apr 2021 23:36:54 -0400 Received: from mail.loongson.cn ([114.242.206.163]:59748 "EHLO loongson.cn" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S234733AbhDVDgu (ORCPT ); Wed, 21 Apr 2021 23:36:50 -0400 Received: from linux.localdomain (unknown [113.200.148.30]) by mail.loongson.cn (Coremail) with SMTP id AQAAf9Dxv+4i74BgpyMMAA--.4298S2; Thu, 22 Apr 2021 11:36:02 +0800 (CST) From: Tiezhu Yang To: Jonathan Corbet , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh Cc: Jesper Dangaard Brouer , linux-doc@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org, Xuefeng Li Subject: [PATCH bpf-next v3] bpf: Fix some invalid links in bpf_devel_QA.rst Date: Thu, 22 Apr 2021 11:36:00 +0800 Message-Id: <1619062560-30483-1-git-send-email-yangtiezhu@loongson.cn> X-Mailer: git-send-email 2.1.0 X-CM-TRANSID: AQAAf9Dxv+4i74BgpyMMAA--.4298S2 X-Coremail-Antispam: 1UD129KBjvJXoWxuryDGr45XFW7Kr43GrW3KFg_yoW5tF1xpa 1fJw4a9r18Wr1fW3ykGr4UCrySqas3GayUCFn7JrZ5Zw1jvF92qr4S9r4rXa98Gryq9F43 A34SkryY9a18ZrDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU9014x267AKxVW8JVW5JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26ryj6F1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26F4j 6r4UJwA2z4x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjcxK6I8E87Iv6xkF7I0E14v26r xl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI64kE6c02F40Ex7xfMcIj 6xIIjxv20xvE14v26r106r15McIj6I8E87Iv67AKxVW8JVWxJwAm72CE4IkC6x0Yz7v_Jr 0_Gr1lF7xvr2IYc2Ij64vIr41lF7I21c0EjII2zVCS5cI20VAGYxC7M4IIrI8v6xkF7I0E 8cxan2IY04v7MxkIecxEwVAFwVW8GwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbV WUJVW8JwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF 67kF1VAFwI0_Jw0_GFylIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42 IY6xIIjxv20xvEc7CjxVAFwI0_Gr0_Cr1lIxAIcVCF04k26cxKx2IYs7xG6rWUJVWrZr1U MIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr0_Gr1UYxBIda VFxhVjvjDU0xZFpf9x0JUa0PhUUUUU= X-CM-SenderInfo: p1dqw3xlh2x3gn0dqz5rrqw2lrqou0/ Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There exist some errors "404 Not Found" when I click the link of "MAINTAINERS" [1], "samples/bpf/" [2] and "selftests" [3] in the documentation "HOWTO interact with BPF subsystem" [4]. As Alexei Starovoitov suggested, just remove "MAINTAINERS" and "samples/bpf/" links and use correct link of "selftests". [1] https://www.kernel.org/doc/html/MAINTAINERS [2] https://www.kernel.org/doc/html/samples/bpf/ [3] https://www.kernel.org/doc/html/tools/testing/selftests/bpf/ [4] https://www.kernel.org/doc/html/latest/bpf/bpf_devel_QA.html Fixes: 542228384888 ("bpf, doc: convert bpf_devel_QA.rst to use RST formatting") Signed-off-by: Tiezhu Yang --- v3: Remove "MAINTAINERS" and "samples/bpf/" links and use correct link of "selftests" v2: Add Fixes: tag Documentation/bpf/bpf_devel_QA.rst | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst index 2ed89ab..d05e67e 100644 --- a/Documentation/bpf/bpf_devel_QA.rst +++ b/Documentation/bpf/bpf_devel_QA.rst @@ -29,7 +29,7 @@ list: This may also include issues related to XDP, BPF tracing, etc. Given netdev has a high volume of traffic, please also add the BPF -maintainers to Cc (from kernel MAINTAINERS_ file): +maintainers to Cc (from kernel ``MAINTAINERS`` file): * Alexei Starovoitov * Daniel Borkmann @@ -234,11 +234,11 @@ be subject to change. Q: samples/bpf preference vs selftests? --------------------------------------- -Q: When should I add code to `samples/bpf/`_ and when to BPF kernel -selftests_ ? +Q: When should I add code to ``samples/bpf/`` and when to BPF kernel +selftests_? A: In general, we prefer additions to BPF kernel selftests_ rather than -`samples/bpf/`_. The rationale is very simple: kernel selftests are +``samples/bpf/``. The rationale is very simple: kernel selftests are regularly run by various bots to test for kernel regressions. The more test cases we add to BPF selftests, the better the coverage @@ -246,9 +246,9 @@ and the less likely it is that those could accidentally break. It is not that BPF kernel selftests cannot demo how a specific feature can be used. -That said, `samples/bpf/`_ may be a good place for people to get started, +That said, ``samples/bpf/`` may be a good place for people to get started, so it might be advisable that simple demos of features could go into -`samples/bpf/`_, but advanced functional and corner-case testing rather +``samples/bpf/``, but advanced functional and corner-case testing rather into kernel selftests. If your sample looks like a test case, then go for BPF kernel selftests @@ -645,10 +645,9 @@ when: .. Links .. _Documentation/process/: https://www.kernel.org/doc/html/latest/process/ -.. _MAINTAINERS: ../../MAINTAINERS .. _netdev-FAQ: ../networking/netdev-FAQ.rst -.. _samples/bpf/: ../../samples/bpf/ -.. _selftests: ../../tools/testing/selftests/bpf/ +.. _selftests: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/ .. _Documentation/dev-tools/kselftest.rst: https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html .. _Documentation/bpf/btf.rst: btf.rst -- 2.1.0