public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tero Kristo <tero.kristo@linux.intel.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/2] bpf: Absolute timer support
Date: Fri, 03 Mar 2023 07:10:18 +0000	[thread overview]
Message-ID: <167782741813.30686.8858379957905019546.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230302114614.2985072-1-tero.kristo@linux.intel.com>

Hello:

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

On Thu,  2 Mar 2023 13:46:12 +0200 you wrote:
> Hi,
> 
> v2 of this series just adds the selftest support. Patch #1 is modified
> slightly (bpf.h modified under tools/include) so that the new selftest
> compiles properly. I also added suggested-by tag from Artem whom I
> forgot to add in the initial upstream post.
> 
> [...]

Here is the summary with links:
  - [PATCHv2,1/2] bpf: Add support for absolute value BPF timers
    https://git.kernel.org/bpf/bpf-next/c/f71f8530494b
  - [PATCHv2,2/2] selftests/bpf: Add absolute timer test
    https://git.kernel.org/bpf/bpf-next/c/944459e88b4f

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



      parent reply	other threads:[~2023-03-03  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 11:46 [PATCHv2 0/2] bpf: Absolute timer support Tero Kristo
2023-03-02 11:46 ` [PATCHv2 1/2] bpf: Add support for absolute value BPF timers Tero Kristo
2023-03-02 11:46 ` [PATCHv2 2/2] selftests/bpf: Add absolute timer test Tero Kristo
2023-03-03  7:10 ` 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=167782741813.30686.8858379957905019546.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=linux-kernel@vger.kernel.org \
    --cc=tero.kristo@linux.intel.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