All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Sync comments for bpf_get_stack
Date: Tue, 29 Mar 2022 02:20:12 +0000	[thread overview]
Message-ID: <164852041255.3757.11920454122901613646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ce54617746b7ed5e9ba3b844e55e74cb8a60e0b5.1648110794.git.geliang.tang@suse.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 24 Mar 2022 16:37:32 +0800 you wrote:
> Commit ee2a098851bf missed updating the comments for helper bpf_get_stack
> in tools/include/uapi/linux/bpf.h. Sync it.
> 
> Fixes: ee2a098851bf ("bpf: Adjust BPF stack helper functions to accommodate skip > 0")
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> ---
>  tools/include/uapi/linux/bpf.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

Here is the summary with links:
  - [bpf-next] bpf: Sync comments for bpf_get_stack
    https://git.kernel.org/bpf/bpf/c/98870605b374

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



      parent reply	other threads:[~2022-03-29  2:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  8:37 [PATCH bpf-next] bpf: Sync comments for bpf_get_stack Geliang Tang
2022-03-24  9:57 ` bpf: Sync comments for bpf_get_stack: Tests Results MPTCP CI
2022-03-24 18:37 ` [PATCH bpf-next] bpf: Sync comments for bpf_get_stack Martin KaFai Lau
2022-03-29  2:20 ` 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=164852041255.3757.11920454122901613646.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=daniel@iogearbox.net \
    --cc=geliang.tang@suse.com \
    --cc=mptcp@lists.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.