From: patchwork-bot+netdevbpf@kernel.org
To: Quan Tian <qtian@vmware.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, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf] docs/bpf: update out-of-date doc in BPF flow dissector
Date: Wed, 13 Sep 2023 21:30:25 +0000 [thread overview]
Message-ID: <169464062596.8992.16050814156574407725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230911152353.8280-1-qtian@vmware.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 11 Sep 2023 15:23:53 +0000 you wrote:
> Commit a5e2151ff9d5 ("net/ipv6: SKB symmetric hash should incorporate
> transport ports") removed the use of FLOW_DISSECTOR_F_STOP_AT_FLOW_LABEL
> in __skb_get_hash_symmetric(), making the doc out-of-date.
>
> Signed-off-by: Quan Tian <qtian@vmware.com>
> ---
> Documentation/bpf/prog_flow_dissector.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [bpf] docs/bpf: update out-of-date doc in BPF flow dissector
https://git.kernel.org/bpf/bpf-next/c/558c50cc3b13
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-09-13 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 15:23 [PATCH bpf] docs/bpf: update out-of-date doc in BPF flow dissector Quan Tian
2023-09-13 21: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=169464062596.8992.16050814156574407725.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=qtian@vmware.com \
--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