From: John Fastabend <john.fastabend@gmail.com>
To: Quentin Monnet <quentin@isovalent.com>,
Yuan Can <yuancan@huawei.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: Thu, 29 Sep 2022 18:56:03 -0700 [thread overview]
Message-ID: <63364cb325f98_233df2084d@john.notmuch> (raw)
In-Reply-To: <fa36f8bf-f111-152d-6a8a-c50be49f1e72@isovalent.com>
Quentin Monnet wrote:
> Wed Sep 28 2022 10:04:38 GMT+0100 (British Summer Time) ~ Yuan Can
> <yuancan@huawei.com>
> > 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(-)
> >
>
> Reviewed-by: Quentin Monnet <quentin@isovalent.com>
>
> Thanks for the clean-up.
> Quentin
lgtm
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2022-09-30 1:56 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 [this message]
2022-09-30 21:10 ` patchwork-bot+netdevbpf
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=63364cb325f98_233df2084d@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.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.