BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, memxor@gmail.com
Subject: Re: [PATCH bpf v4 0/2] bpf: fix a bpf_timer initialization issue
Date: Fri, 11 Feb 2022 21:30:10 +0000	[thread overview]
Message-ID: <164461501038.10199.4843368758097321221.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220211194943.3141324-1-yhs@fb.com>

Hello:

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

On Fri, 11 Feb 2022 11:49:43 -0800 you wrote:
> The patch [1] exposed a bpf_timer initialization bug in function
> check_and_init_map_value(). With bug fix here, the patch [1]
> can be applied with all selftests passed. Please see individual
> patches for fix details.
> 
>   [1] https://lore.kernel.org/bpf/20220209070324.1093182-2-memxor@gmail.com/
> 
> [...]

Here is the summary with links:
  - [bpf,v4,1/2] bpf: emit bpf_timer in vmlinux BTF
    https://git.kernel.org/bpf/bpf/c/3bd916ee0ecb
  - [bpf,v4,2/2] bpf: fix a bpf_timer initialization issue
    https://git.kernel.org/bpf/bpf/c/5eaed6eedbe9

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-02-11 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 19:49 [PATCH bpf v4 0/2] bpf: fix a bpf_timer initialization issue Yonghong Song
2022-02-11 19:49 ` [PATCH bpf v4 1/2] bpf: emit bpf_timer in vmlinux BTF Yonghong Song
2022-02-11 19:49 ` [PATCH bpf v4 2/2] bpf: fix a bpf_timer initialization issue Yonghong Song
2022-02-11 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=164461501038.10199.4843368758097321221.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=kernel-team@fb.com \
    --cc=memxor@gmail.com \
    --cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox