public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpf: Two small cleanups
Date: Fri, 03 Feb 2023 04:50:17 +0000	[thread overview]
Message-ID: <167539981709.16316.14082640306773114847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1675319486-27744-1-git-send-email-yangtiezhu@loongson.cn>

Hello:

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

On Thu,  2 Feb 2023 14:31:24 +0800 you wrote:
> Tiezhu Yang (2):
>   tools/bpf: Use tab instead of white spaces to sync bpf.h
>   selftests/bpf: Use semicolon instead of comma in test_verifier.c
> 
>  tools/include/uapi/linux/bpf.h              | 4 ++--
>  tools/testing/selftests/bpf/test_verifier.c | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)

Here is the summary with links:
  - [bpf-next,1/2] tools/bpf: Use tab instead of white spaces to sync bpf.h
    https://git.kernel.org/bpf/bpf-next/c/e2bd9742989b
  - [bpf-next,2/2] selftests/bpf: Use semicolon instead of comma in test_verifier.c
    https://git.kernel.org/bpf/bpf-next/c/150809082aab

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-02-03  4:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  6:31 [PATCH bpf-next 0/2] bpf: Two small cleanups Tiezhu Yang
2023-02-02  6:31 ` [PATCH bpf-next 1/2] tools/bpf: Use tab instead of white spaces to sync bpf.h Tiezhu Yang
2023-02-02  6:31 ` [PATCH bpf-next 2/2] selftests/bpf: Use semicolon instead of comma in test_verifier.c Tiezhu Yang
2023-02-03  4:50 ` 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=167539981709.16316.14082640306773114847.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=yangtiezhu@loongson.cn \
    /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