From: Greg KH <gregkh@linuxfoundation.org>
To: Suleiman Souhlal <suleiman@google.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Ian Rogers <irogers@google.com>,
ssouhlal@freebsd.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [RESEND][PATCH] tools/resolve_btfids: Fix build when cross compiling kernel with clang.
Date: Fri, 6 Jun 2025 09:36:51 +0200 [thread overview]
Message-ID: <2025060617-citation-greedy-ba05@gregkh> (raw)
In-Reply-To: <CABCjUKB4OgQoGv+Eg7q3zmJXXw8dWfEo_AP-XfzxHDoodtxhXg@mail.gmail.com>
On Fri, Jun 06, 2025 at 03:21:45PM +0900, Suleiman Souhlal wrote:
> On Fri, Jun 6, 2025 at 3:20 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, Jun 06, 2025 at 03:08:09PM +0900, Suleiman Souhlal wrote:
> > > On Fri, Jun 6, 2025 at 3:05 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > On Fri, Jun 06, 2025 at 02:36:50PM +0900, Suleiman Souhlal wrote:
> > > > > When cross compiling the kernel with clang, we need to override
> > > > > CLANG_CROSS_FLAGS when preparing the step libraries for
> > > > > resolve_btfids.
> > > > >
> > > > > Prior to commit d1d096312176 ("tools: fix annoying "mkdir -p ..." logs
> > > > > when building tools in parallel"), MAKEFLAGS would have been set to a
> > > > > value that wouldn't set a value for CLANG_CROSS_FLAGS, hiding the
> > > > > fact that we weren't properly overriding it.
> > > > >
> > > > > Cc: stable@vger.kernel.org
> > > > > Fixes: 56a2df7615fa ("tools/resolve_btfids: Compile resolve_btfids as host program")
> > > > > Signed-off-by: Suleiman Souhlal <suleiman@google.com>
> > > > > ---
> > > > > tools/bpf/resolve_btfids/Makefile | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > You forgot to say why this is a resend :(
> > >
> > > I wasn't sure how to say it. It didn't occur to me that I could have
> > > replied to it with the reason.
> >
> > That goes below the --- line and it would be a v2, not a RESEND as you
> > changed something:
> >
> > > It was because I had "Signed-of-by:" instead of "Signed-off-by:".
> >
> > Which means it was not identical to the first version (a RESEND means a
> > maintainer can take either as they are the same).
>
> Ah. Should I resend it as a v2?
Think about what you would want to see if you were on the recieving end
of thousands of patches and had to try to figure out what to ignore and
what to pay attention to...
thanks,
greg k-h
prev parent reply other threads:[~2025-06-06 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 5:23 [PATCH] tools/resolve_btfids: Fix build when cross compiling kernel with clang Suleiman Souhlal
2025-06-06 5:36 ` [RESEND][PATCH] " Suleiman Souhlal
2025-06-06 6:05 ` Greg KH
2025-06-06 6:08 ` Suleiman Souhlal
2025-06-06 6:20 ` Greg KH
2025-06-06 6:21 ` Suleiman Souhlal
2025-06-06 7:36 ` Greg KH [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=2025060617-citation-greedy-ba05@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=masahiroy@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=ssouhlal@freebsd.org \
--cc=stable@vger.kernel.org \
--cc=suleiman@google.com \
--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