Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 16 Sep 2022 13:26:27 -0700
From:   Peilin Ye <yepeilin.cs@gmail.com>
To:     Martin KaFai Lau <martin.lau@linux.dev>
Cc:     Peilin Ye <peilin.ye@bytedance.com>,
        Alexei Starovoitov <ast@kernel.org>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Andrii Nakryiko <andrii@kernel.org>,
        Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
        John Fastabend <john.fastabend@gmail.com>,
        KP Singh <kpsingh@kernel.org>,
        Stanislav Fomichev <sdf@google.com>,
        Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>,
        bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf/btf: Use btf_type_str() whenever possible
Message-ID: <20220916202627.GA31382@bytedance>
References: <20220914021328.17039-1-yepeilin.cs@gmail.com>
 <7c01a2b8-bfb7-df72-faae-0b940ea0f149@linux.dev>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7c01a2b8-bfb7-df72-faae-0b940ea0f149@linux.dev>
Precedence: bulk

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