All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yuan Can <yuancan@huawei.com>
Cc: quentin@isovalent.com, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	sdf@google.com, haoluo@google.com, jolsa@kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH 0/2] tools: bpftool: Remove unused struct
Date: Fri, 30 Sep 2022 21:10:15 +0000	[thread overview]
Message-ID: <166457221598.29882.2232016600402051935.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220928090440.79637-1-yuancan@huawei.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed, 28 Sep 2022 09:04:38 +0000 you wrote:
> This series contains two cleanup patches, remove unused struct.
> 
> Yuan Can (2):
>   tools: bpftool: Remove unused struct btf_attach_point
>   tools: bpftool: Remove unused struct event_ring_info
> 
>  tools/bpf/bpftool/btf.c           | 5 -----
>  tools/bpf/bpftool/map_perf_ring.c | 7 -------
>  2 files changed, 12 deletions(-)

Here is the summary with links:
  - [1/2] tools: bpftool: Remove unused struct btf_attach_point
    https://git.kernel.org/bpf/bpf-next/c/d863f42930db
  - [2/2] tools: bpftool: Remove unused struct event_ring_info
    https://git.kernel.org/bpf/bpf-next/c/f95a479797dc

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-09-30 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  9:04 [PATCH 0/2] tools: bpftool: Remove unused struct Yuan Can
2022-09-28  9:04 ` [PATCH 1/2] tools: bpftool: Remove unused struct btf_attach_point Yuan Can
2022-09-28  9:04 ` [PATCH 2/2] tools: bpftool: Remove unused struct event_ring_info Yuan Can
2022-09-28  9:30 ` [PATCH 0/2] tools: bpftool: Remove unused struct Quentin Monnet
2022-09-30  1:56   ` John Fastabend
2022-09-30 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=166457221598.29882.2232016600402051935.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=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=quentin@isovalent.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yhs@fb.com \
    --cc=yuancan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.