Typical RST documents embed the reference link straight in the text. Currently document uses a '[1]' with the reference below that paragraph. Use RST :ref:`path/to/file` <label>` format and embed the reference to seccomp_filter directly in the text. Add a label to seccomp_filter.rst to enable the reference to function correctly. Signed-off-by: Tobin C. Harding <me@xxxxxxxx> --- Documentation/networking/filter.rst | 12 ++++++------ Documentation/userspace-api/seccomp_filter.rst | 2 ++ 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/Documentation/networking/filter.rst b/Documentation/networking/filter.rst index 10c4eab042df..1ed6972c3544 100644 --- a/Documentation/networking/filter.rst +++ b/Documentation/networking/filter.rst @@ -43,12 +43,12 @@ internal compiler that generates a structure that can eventually be loaded via SO_ATTACH_FILTER to the kernel. ``tcpdump -i em1 port 22 -ddd`` displays what is being placed into this structure. -Although we were only speaking about sockets here, BPF in Linux is used -in many more places. There's xt_bpf for netfilter, cls_bpf in the kernel -qdisc layer, SECCOMP-BPF (SECure COMPuting [1]), and lots of other places -such as team driver, PTP code, etc where BPF is being used. - - [1] Documentation/userspace-api/seccomp_filter.rst +Although we were only speaking about sockets here, BPF in Linux is used in +many more places. There's xt_bpf for netfilter, cls_bpf in the kernel qdisc +layer, SECCOMP-BPF (SECure COMPuting +:ref:`Documentation/userspace-api/seccomp_filter.rst <seccomp_filter>`), +and lots of other places such as team driver, PTP code, etc where BPF is +being used. Original BPF paper: diff --git a/Documentation/userspace-api/seccomp_filter.rst b/Documentation/userspace-api/seccomp_filter.rst index 82a468bc7560..6c3eb4908818 100644 --- a/Documentation/userspace-api/seccomp_filter.rst +++ b/Documentation/userspace-api/seccomp_filter.rst @@ -2,6 +2,8 @@ Seccomp BPF (SECure COMPuting with filters) =========================================== +.. _seccomp_filter: + Introduction ============ -- 2.17.1 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
