From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: "Hou Tao" <houtao@huaweicloud.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Björn Töpel" <bjorn.topel@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Song Liu" <song@kernel.org>, "Hao Luo" <haoluo@google.com>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"KP Singh" <kpsingh@kernel.org>,
"Stanislav Fomichev" <sdf@google.com>,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next 1/2] bpf, cpumap: Remove unused cmap field from bpf_cpu_map_entry
Date: Fri, 28 Jul 2023 09:38:17 -0700 [thread overview]
Message-ID: <20230728093817.58d5b187@kernel.org> (raw)
In-Reply-To: <ZMOuzBkjFGzHjJNI@krava>
On Fri, 28 Jul 2023 14:04:28 +0200 Jiri Olsa wrote:
> nit, should it have Fixes: cdfafe98cabe ?
I don't think so, Fixes is for people backporting fixes.
next prev parent reply other threads:[~2023-07-28 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 1:49 [PATCH bpf-next 0/2] Remove unused fields in cpumap & devmap Hou Tao
2023-07-28 1:49 ` [PATCH bpf-next 1/2] bpf, cpumap: Remove unused cmap field from bpf_cpu_map_entry Hou Tao
2023-07-28 10:48 ` Jesper Dangaard Brouer
2023-07-28 12:04 ` Jiri Olsa
2023-07-28 16:38 ` Jakub Kicinski [this message]
2023-07-28 1:49 ` [PATCH bpf-next 2/2] bpf, devmap: Remove unused dtab field from bpf_dtab_netdev Hou Tao
2023-07-28 10:48 ` Jesper Dangaard Brouer
2023-08-01 1:58 ` [PATCH bpf-next 0/2] Remove unused fields in cpumap & devmap 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=20230728093817.58d5b187@kernel.org \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).