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] selftests/bpf: Remove not used headers
Date: Wed, 22 Feb 2023 21:10:17 +0000	[thread overview]
Message-ID: <167710021750.10496.4702478918450314201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1676533861-27508-1-git-send-email-yangtiezhu@loongson.cn>

Hello:

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

On Thu, 16 Feb 2023 15:51:01 +0800 you wrote:
> The following three uapi headers:
> 
>     tools/arch/arm64/include/uapi/asm/bpf_perf_event.h
>     tools/arch/s390/include/uapi/asm/bpf_perf_event.h
>     tools/arch/s390/include/uapi/asm/ptrace.h
> 
> were introduced in commit 618e165b2a8e ("selftests/bpf: sync kernel headers
> and introduce arch support in Makefile"), they are not used any more after
> commit 720f228e8d31 ("bpf: fix broken BPF selftest build"), so remove them.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Remove not used headers
    https://git.kernel.org/bpf/bpf-next/c/1f265d2aea0d

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-22 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  7:51 [PATCH bpf-next] selftests/bpf: Remove not used headers Tiezhu Yang
2023-02-16 18:31 ` Stanislav Fomichev
2023-02-17 16:36   ` Daniel Borkmann
2023-02-22 21: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=167710021750.10496.4702478918450314201.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