From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: netdev-bot+sashiko@kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, donald.hunter@gmail.com,
horms@kernel.org, shuah@kernel.org, matttbe@kernel.org,
sdf@fomichev.me, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] tools: ynl: Allow cross-compiling ynl and associated tools
Date: Mon, 7 Sep 2026 10:22:45 +0200 [thread overview]
Message-ID: <d1928f33-23ca-46cd-af71-1f3cdc55bf96@bootlin.com> (raw)
In-Reply-To: <178870681916.219967.14635919564673520317@kernel.org>
Hi,
On 9/6/26 17:00, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 3 potential
> issue(s) to consider:
>
> Critical: 0 · High: 0 · Medium: 2 · Low: 1
[...]
> [Severity: Medium]
> Should the new include come before Makefile.arch rather than after it?
This looks like a legit point
[...]
> [Severity: Medium]
> The commit message says the change accounts for "the cross-compiling options
> such as CROSS_COMPILE or the LLVM-specific variables". Does this also cover
> the documented LLVM form described in Documentation/kbuild/llvm.rst, that is
> make LLVM=1 ARCH=<arch> with no CROSS_COMPILE?
I'll update the commit log to document the limitation
[...]
> [Severity: Low]
> This isn't a bug, but now that Makefile.include is pulled in here, the
> existing Q assignment later in this same file disagrees with it:
Also legit as well.
So, I'll swap the Makefile.arch and Makefile.include inclusions, document in
the commit log that we don't deal with LLVM + no CROSS_COMPILE, and drop the
Q = @
line in ynltool/Makefile.
Matthieu, are you OK with me keeping your review tag with the above changes,
or do I drop it and resend for you to re-review ?
Maxime
next prev parent reply other threads:[~2026-09-07 8:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 15:55 [PATCH net-next v2 0/2] selftests: drv-net: Allow cross-compiling the hardware tests Maxime Chevallier (Netdev Foundation)
2026-09-03 15:55 ` [PATCH net-next v2 1/2] tools: ynl: Allow cross-compiling ynl and associated tools Maxime Chevallier (Netdev Foundation)
2026-09-03 16:22 ` Matthieu Baerts
2026-09-06 15:00 ` netdev-bot+sashiko
2026-09-07 8:22 ` Maxime Chevallier [this message]
2026-09-07 9:36 ` Matthieu Baerts
2026-09-03 15:55 ` [PATCH net-next v2 2/2] selftests: drv-net: Use cross-compilation environment for the io_uring check Maxime Chevallier (Netdev Foundation)
2026-09-03 16:22 ` Matthieu Baerts
2026-09-06 15:00 ` netdev-bot+sashiko
2026-09-07 13:51 ` Maxime Chevallier
2026-09-07 13:58 ` Matthieu Baerts
2026-09-03 16:51 ` [PATCH net-next v2 0/2] selftests: drv-net: Allow cross-compiling the hardware tests Andrew Lunn
2026-09-03 17:25 ` Matthieu Baerts
2026-09-03 21:44 ` Maxime Chevallier
2026-09-03 21:59 ` Andrew Lunn
2026-09-04 6:11 ` Maxime Chevallier
2026-09-03 23:40 ` Jakub Kicinski
2026-09-03 17:11 ` Andrew Lunn
2026-09-03 17:25 ` Matthieu Baerts
2026-09-03 20:55 ` Andrew Lunn
2026-09-04 9:43 ` Matthieu Baerts
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=d1928f33-23ca-46cd-af71-1f3cdc55bf96@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=thomas.petazzoni@bootlin.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.