From: patchwork-bot+netdevbpf@kernel.org
To: Joe Stringer <joe@isovalent.com>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org, corbet@lwn.net,
martin.lau@linux.dev, bagasdotme@gmail.com, maxtram95@gmail.com,
john.fastabend@gmail.com
Subject: Re: [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties
Date: Thu, 27 Apr 2023 12:30:20 +0000 [thread overview]
Message-ID: <168259862024.23031.10502966266346106910.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230422172054.3355436-1-joe@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sat, 22 Apr 2023 10:20:53 -0700 you wrote:
> Depending on the map type and flags for LRU, different properties are
> global or percpu. Add a table to describe these.
>
> Signed-off-by: Joe Stringer <joe@isovalent.com>
> ---
> v5: Use bold rather than verbatim for column header
> v4: Initial posting
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/2] docs/bpf: Add table to describe LRU properties
https://git.kernel.org/bpf/bpf-next/c/af0335d2926e
- [bpf-next,v5,2/2] docs/bpf: Add LRU internals description and graph
https://git.kernel.org/bpf/bpf-next/c/1a986518b8a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-27 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 17:20 [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties Joe Stringer
2023-04-22 17:20 ` [PATCH bpf-next v5 2/2] docs/bpf: Add LRU internals description and graph Joe Stringer
2023-04-23 14:26 ` John Fastabend
2023-04-23 14:26 ` [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties John Fastabend
2023-04-27 12:30 ` 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=168259862024.23031.10502966266346106910.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=joe@isovalent.com \
--cc=john.fastabend@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=maxtram95@gmail.com \
/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.