From: David Vernet <void@manifault.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
hch@infradead.org, hawkinsw@obs.cr, dthaler@microsoft.com,
bpf@ietf.org
Subject: [PATCH bpf-next 1/3] bpf,docs: Move linux-notes.rst to root bpf docs tree
Date: Mon, 28 Aug 2023 10:59:46 -0500 [thread overview]
Message-ID: <20230828155948.123405-2-void@manifault.com> (raw)
In-Reply-To: <20230828155948.123405-1-void@manifault.com>
In commit 4d496be9ca05 ("bpf,docs: Create new standardization
subdirectory"), I added a standardization/ directory to the BPF
documentation, which will contain the docs that will be standardized as
part of the effort with the IETF.
I included linux-notes.rst in that directory, but I shouldn't have. It
doesn't contain anything that will be standardized. Let's move it back
to Documentation/bpf.
Signed-off-by: David Vernet <void@manifault.com>
---
Documentation/bpf/index.rst | 1 +
Documentation/bpf/{standardization => }/linux-notes.rst | 0
Documentation/bpf/standardization/index.rst | 1 -
3 files changed, 1 insertion(+), 1 deletion(-)
rename Documentation/bpf/{standardization => }/linux-notes.rst (100%)
diff --git a/Documentation/bpf/index.rst b/Documentation/bpf/index.rst
index 1ff177b89d66..aeaeb35e6d4a 100644
--- a/Documentation/bpf/index.rst
+++ b/Documentation/bpf/index.rst
@@ -29,6 +29,7 @@ that goes into great technical depth about the BPF Architecture.
bpf_licensing
test_debug
clang-notes
+ linux-notes
other
redirect
diff --git a/Documentation/bpf/standardization/linux-notes.rst b/Documentation/bpf/linux-notes.rst
similarity index 100%
rename from Documentation/bpf/standardization/linux-notes.rst
rename to Documentation/bpf/linux-notes.rst
diff --git a/Documentation/bpf/standardization/index.rst b/Documentation/bpf/standardization/index.rst
index 09c6ba055fd7..d7b946f71261 100644
--- a/Documentation/bpf/standardization/index.rst
+++ b/Documentation/bpf/standardization/index.rst
@@ -12,7 +12,6 @@ for the working group charter, documents, and more.
:maxdepth: 1
instruction-set
- linux-notes
.. Links:
.. _IETF BPF Working Group: https://datatracker.ietf.org/wg/bpf/about/
--
2.41.0
next prev parent reply other threads:[~2023-08-28 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 15:59 [PATCH bpf-next 0/3] Clean up some standardization stuff David Vernet
2023-08-28 15:59 ` David Vernet [this message]
2023-08-28 15:59 ` [PATCH bpf-next 2/3] bpf,docs: Add abi.rst document to standardization subdirectory David Vernet
2023-08-28 15:59 ` [PATCH bpf-next 3/3] bpf,docs: s/eBPF/BPF in standards documents David Vernet
2023-08-30 14:40 ` [PATCH bpf-next 0/3] Clean up some standardization stuff patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230828155948.123405-2-void@manifault.com \
--to=void@manifault.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dthaler@microsoft.com \
--cc=haoluo@google.com \
--cc=hawkinsw@obs.cr \
--cc=hch@infradead.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox