From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vfedorenko@novek.ru>
Cc: kafai@fb.com, andrii.nakryiko@gmail.com, daniel@iogearbox.net,
ast@kernel.org, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] add hwtstamp to __sk_buff
Date: Fri, 10 Sep 2021 21:30:06 +0000 [thread overview]
Message-ID: <163130940657.19089.1279931064701174947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210909220409.8804-1-vfedorenko@novek.ru>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 10 Sep 2021 01:04:07 +0300 you wrote:
> This patch set adds hardware timestamps to __sk_buff. The first patch
> implements feature, the second one adds a selftest.
>
> v2 -> v3:
> * rebase on bpf-next
>
> v1 -> v2:
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: add hardware timestamp field to __sk_buff
https://git.kernel.org/bpf/bpf-next/c/f64c4acea51f
- [bpf-next,v3,2/2] selftests/bpf: test new __sk_buff field hwtstamp
https://git.kernel.org/bpf/bpf-next/c/3384c7c7641b
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:[~2021-09-10 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 22:04 [PATCH bpf-next v3 0/2] add hwtstamp to __sk_buff Vadim Fedorenko
2021-09-09 22:04 ` [PATCH bpf-next v3 1/2] bpf: add hardware timestamp field " Vadim Fedorenko
2021-09-09 22:04 ` [PATCH bpf-next v3 2/2] selftests/bpf: test new __sk_buff field hwtstamp Vadim Fedorenko
2021-09-10 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=163130940657.19089.1279931064701174947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=vfedorenko@novek.ru \
--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;
as well as URLs for NNTP newsgroup(s).