mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Ilya Maximets <i.maximets@ovn.org>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Shuah Khan <shuah@kernel.org>, David Ahern <dsahern@kernel.org>,
	Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH net 0/2] selftests: net: use KHDR_INCLUDES in CFLAGS
Date: Tue, 8 Sep 2026 17:28:21 +0200	[thread overview]
Message-ID: <8432a0fa-0aa1-40ee-919e-6dcc05aeea4c@kernel.org> (raw)
In-Reply-To: <20260904115127.1c316a33@kernel.org>

Hi Jakub,

On 04/09/2026 20:51, Jakub Kicinski wrote:
> On Fri, 4 Sep 2026 20:20:44 +0200 Matthieu Baerts wrote:
>> These patches didn't get picked up in the tests because the Clang build
>> failed with Rust code:
>>
>> https://netdev-ctrl.bots.linux.dev/logs/build/1158213/14791779/build_clang/stderr
>>
>> I only modified the selftests here. Other patches sent before me have
>> the same issue, but some sent after don't. One of those "random" issues
>> on the build server?
> 
> kbuild / tools build likes to sometimes pick up the wrong source tree
> if you have a worktree nested inside a git repo :/
> Here the Rust build was partially using the sources from the main repo
> and partially from the work tree.
> I'll push a NIPA workaround to sync the main repo to something recent
> it should paper over this bug. It's not the first time it happened.

Thank you for the explanation, and for the fix!

I was checking if I had to resend this series for the CI, but it looks
like these patches have been taken by the "brancher" service, e.g.

- https://github.com/linux-netdev/testing/commit/93408c0627c0
- https://github.com/linux-netdev/testing/commit/82fe019a07b0

Maybe they are there after the few hickups due to PW's update?

(It is not clear why it says there is a conflict, but I guess that's
because the contest job didn't override the status for the same reasons.)

Anyway, no need to re-send them then. Or should I?

Cheers,
Matt

  reply	other threads:[~2026-09-08 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 16:13 Matthieu Baerts (NGI0)
2026-09-04 16:13 ` [PATCH net 1/2] selftests: netfilter: " Matthieu Baerts (NGI0)
2026-09-04 16:41   ` Ilya Maximets
2026-09-04 16:55     ` Matthieu Baerts
2026-09-04 16:13 ` [PATCH net 2/2] selftests: forwarding: " Matthieu Baerts (NGI0)
2026-09-04 16:44   ` Ilya Maximets
2026-09-04 18:20 ` [PATCH net 0/2] selftests: net: " Matthieu Baerts
2026-09-04 18:51   ` Jakub Kicinski
2026-09-08 15:28     ` Matthieu Baerts [this message]
2026-09-09 21:00 ` 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=8432a0fa-0aa1-40ee-919e-6dcc05aeea4c@kernel.org \
    --to=matttbe@kernel.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    --cc=shuah@kernel.org \
    /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

all inboxes | Powered by JetHome®