From: patchwork-bot+netdevbpf@kernel.org
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
joannelkoong@gmail.com, jolsa@kernel.org, davemarchevsky@fb.com,
lorenzo@kernel.org, geliang.tang@suse.com, jakub@cloudflare.com,
netdev@vger.kernel.org, bpf@vger.kernel.org, tglx@linutronix.de,
maciej.fijalkowski@intel.com, brouer@redhat.com
Subject: Re: [PATCH bpf-next v2 0/2] Add BPF-helper for accessing CLOCK_TAI
Date: Tue, 09 Aug 2022 17:00:14 +0000 [thread overview]
Message-ID: <166006441427.21395.6653949715858271839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220809060803.5773-1-kurt@linutronix.de>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 9 Aug 2022 08:08:01 +0200 you wrote:
> Hi,
>
> add a BPF-helper for accessing CLOCK_TAI. Use cases for such a BPF helper
> include functionalities such as Tx launch time (e.g. ETF and TAPRIO Qdiscs),
> timestamping and policing.
>
> Patch #1 - Introduce BPF helper
> Patch #2 - Add test case (skb based)
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Add BPF-helper for accessing CLOCK_TAI
https://git.kernel.org/bpf/bpf-next/c/c8996c98f703
- [bpf-next,v2,2/2] selftests/bpf: Add BPF-helper test for CLOCK_TAI access
https://git.kernel.org/bpf/bpf-next/c/64e15820b987
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:[~2022-08-09 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 6:08 [PATCH bpf-next v2 0/2] Add BPF-helper for accessing CLOCK_TAI Kurt Kanzenbach
2022-08-09 6:08 ` [PATCH bpf-next v2 1/2] bpf: " Kurt Kanzenbach
2022-08-09 6:08 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add BPF-helper test for CLOCK_TAI access Kurt Kanzenbach
2022-08-09 17:00 ` 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=166006441427.21395.6653949715858271839.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=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=geliang.tang@suse.com \
--cc=jakub@cloudflare.com \
--cc=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kurt@linutronix.de \
--cc=lorenzo@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--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