All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, 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: Re: [PATCH bpf-next 0/3] Clean up some standardization stuff
Date: Wed, 30 Aug 2023 14:40:22 +0000	[thread overview]
Message-ID: <169340642234.1057.1251981139768787311.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230828155948.123405-1-void@manifault.com>

Hello:

This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Mon, 28 Aug 2023 10:59:45 -0500 you wrote:
> The Documentation/bpf/standardization subdirectory contains documents
> that will be standardized with the IETF. There are a few things we can
> do to clean it up:
> 
> - Move linux-notes.rst back to Documentation/bpf. It doesn't belong in
>   the standardization directory.
> - Move ABI-specific verbiage from instruction-set.rst into a new abi.rst
>   document. This document will be expanded significantly over time. For
>   now, we just need to get anything describing ABI out of
>   instruction-set.rst.
> - Say BPF instead of eBPF in our documents. It's just creating
>   confusion.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/3] bpf,docs: Move linux-notes.rst to root bpf docs tree
    https://git.kernel.org/bpf/bpf/c/aee1720eeb87
  - [bpf-next,2/3] bpf,docs: Add abi.rst document to standardization subdirectory
    https://git.kernel.org/bpf/bpf/c/deb884072546
  - [bpf-next,3/3] bpf,docs: s/eBPF/BPF in standards documents
    https://git.kernel.org/bpf/bpf/c/7d35eb1a184a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-08-30 14:40 UTC|newest]

Thread overview: 9+ 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 ` [Bpf] " David Vernet
2023-08-28 15:59 ` [PATCH bpf-next 1/3] bpf,docs: Move linux-notes.rst to root bpf docs tree David Vernet
2023-08-28 15:59   ` [Bpf] [PATCH bpf-next 1/3] bpf, docs: " David Vernet
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   ` [Bpf] [PATCH bpf-next 2/3] bpf, docs: " David Vernet
2023-08-28 15:59 ` [PATCH bpf-next 3/3] bpf,docs: s/eBPF/BPF in standards documents David Vernet
2023-08-28 15:59   ` [Bpf] [PATCH bpf-next 3/3] bpf, docs: " David Vernet
2023-08-30 14:40 ` patchwork-bot+netdevbpf [this message]

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=169340642234.1057.1251981139768787311.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=void@manifault.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.