[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220916202627.GA31382@bytedance>
Date: Fri, 16 Sep 2022 13:26:27 -0700
From: Peilin Ye <yepeilin.cs@...il.com>
To: Martin KaFai Lau <martin.lau@...ux.dev>
Cc: Peilin Ye <peilin.ye@...edance.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next] bpf/btf: Use btf_type_str() whenever possible
On Fri, Sep 16, 2022 at 11:37:46AM -0700, Martin KaFai Lau wrote:
> This clean up makes sense. The patch cannot be applied though [0], so it is
> marked as 'Changes Requested'. Also, where is the cad4657ba2ce coming from?
> It can't be found in the bpf-next tree. Please rebase on the bpf-next and
> resend.
Ah, I will fix it in v2 soon.
Thanks,
Peilin Ye
Powered by blists - more mailing lists