From: Jakub Kicinski <kuba@kernel.org>
To: Petr Machata <petrm@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"netdev-driver-reviewers@vger.kernel.org"
<netdev-driver-reviewers@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [ANN] net-next is OPEN
Date: Tue, 23 Jan 2024 07:34:12 -0800 [thread overview]
Message-ID: <20240123073412.063bc08e@kernel.org> (raw)
In-Reply-To: <87fryonx35.fsf@nvidia.com>
On Tue, 23 Jan 2024 10:55:09 +0100 Petr Machata wrote:
> > If you authored any net or drivers/net selftests, please look around
> > and see if they are passing. If not - send patches or LMK what I need
> > to do to make them pass on the runner.. Make sure to scroll down to
> > the "Not reporting to patchwork" section.
>
> A whole bunch of them fail because of no IPv6 support in the runner
> kernel. E.g. this from bridge-mdb.sh[0]:
Thanks a lot for investigating! I take it that you're looking at
forwarding? Please send a patch to add the missing configs to
tools/testing/selftests/net/forwarding/config
The runner uses that to configure the kernel on top of defconfig.
Unless I'm doing it wrong and the sub-directories are supposed to
inherit the parent directory's config? So net/forwarding/ should
be built with net/'s config? I could not find the info in docs,
does anyone know?
next parent reply other threads:[~2024-01-23 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240122091612.3f1a3e3d@kernel.org>
[not found] ` <87fryonx35.fsf@nvidia.com>
2024-01-23 15:34 ` Jakub Kicinski [this message]
2024-01-23 17:04 ` [ANN] net-next is OPEN Petr Machata
2024-01-23 17:38 ` Jakub Kicinski
2024-01-24 11:06 ` Petr Machata
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=20240123073412.063bc08e@kernel.org \
--to=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--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