BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang.tang@suse.com>
Cc: shuah@kernel.org, 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,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/2] drop duplicate max/min definitions
Date: Mon, 11 Apr 2022 15:30:14 +0000	[thread overview]
Message-ID: <164969101435.5829.13061515583824165618.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1649462033.git.geliang.tang@suse.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sat,  9 Apr 2022 07:58:16 +0800 you wrote:
> Two small cleanups for selftests, drop duplicate max/min definitions.
> 
> v3:
>  - move '#include <sys/param.h>' into test_progs.h.
> 
> v2:
>  - do more cleanups as Daniel suggested.
> 
> [...]

Here is the summary with links:
  - [v3,1/2] selftests: bpf: drop duplicate max/min definitions
    https://git.kernel.org/bpf/bpf-next/c/f4fd706f7383
  - [v3,2/2] selftests: mqueue: drop duplicate min definition
    (no matching commit)

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-04-11 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 23:58 [PATCH v3 0/2] drop duplicate max/min definitions Geliang Tang
2022-04-08 23:58 ` [PATCH v3 1/2] selftests: bpf: " Geliang Tang
2022-04-11  5:23   ` Song Liu
2022-04-08 23:58 ` [PATCH v3 2/2] selftests: mqueue: drop duplicate min definition Geliang Tang
2022-04-11 15: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=164969101435.5829.13061515583824165618.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=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=songliubraving@fb.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