From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
<adrian.pielech@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Krzysztof Galazka <krzysztof.galazka@intel.com>
Subject: Re: [Intel-wired-lan] [ANN] intel's netdev-ci
Date: Thu, 4 Dec 2025 08:20:49 -0800 [thread overview]
Message-ID: <20251204082049.1ecfd15f@kernel.org> (raw)
In-Reply-To: <20251204082001.561a5f3b@kernel.org>
On Thu, 4 Dec 2025 08:20:01 -0800 Jakub Kicinski wrote:
> On Thu, 4 Dec 2025 13:59:34 +0100 Przemek Kitszel wrote:
> > Hi all!
> >
> > I'm pleased to announce that we have set up infrastructure for testing
> > netdev on our e810 NICs, with more to come.
> >
> > Big thanks to Adrian Pielech who made substantial effort to make this
> > possible and to Krzysztof Gałązka for the initial PoC work.
> >
> > This work plugs into netdev-ci initiative by netdev maintainers,
> > to run kselftests (mostly functional tests in python) against current
> > proposed net-next branch, on real hardware.
>
> Thank you for doing this work! I really appreciate participation
> in the community testing efforts.
>
> > Our results are here:
> > https://netdev-ci-results.intel.com/ice-results/results.json
> >
> > with a viewer for humans:
> > https://netdev-ci-results.intel.com/
>
> Very neat UI :)
>
> Are you planning to stay on the SW branch stream? I was anticipating
> that HW testing will need a lower frequency of branches hence the
> existence of the:
https://netdev.bots.linux.dev/static/nipa/branches-hw.json
HW branch stream.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
<adrian.pielech@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Krzysztof Galazka <krzysztof.galazka@intel.com>
Subject: Re: [ANN] intel's netdev-ci
Date: Thu, 4 Dec 2025 08:20:49 -0800 [thread overview]
Message-ID: <20251204082049.1ecfd15f@kernel.org> (raw)
In-Reply-To: <20251204082001.561a5f3b@kernel.org>
On Thu, 4 Dec 2025 08:20:01 -0800 Jakub Kicinski wrote:
> On Thu, 4 Dec 2025 13:59:34 +0100 Przemek Kitszel wrote:
> > Hi all!
> >
> > I'm pleased to announce that we have set up infrastructure for testing
> > netdev on our e810 NICs, with more to come.
> >
> > Big thanks to Adrian Pielech who made substantial effort to make this
> > possible and to Krzysztof Gałązka for the initial PoC work.
> >
> > This work plugs into netdev-ci initiative by netdev maintainers,
> > to run kselftests (mostly functional tests in python) against current
> > proposed net-next branch, on real hardware.
>
> Thank you for doing this work! I really appreciate participation
> in the community testing efforts.
>
> > Our results are here:
> > https://netdev-ci-results.intel.com/ice-results/results.json
> >
> > with a viewer for humans:
> > https://netdev-ci-results.intel.com/
>
> Very neat UI :)
>
> Are you planning to stay on the SW branch stream? I was anticipating
> that HW testing will need a lower frequency of branches hence the
> existence of the:
https://netdev.bots.linux.dev/static/nipa/branches-hw.json
HW branch stream.
next prev parent reply other threads:[~2025-12-04 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 12:59 [Intel-wired-lan] [ANN] intel's netdev-ci Przemek Kitszel
2025-12-04 12:59 ` Przemek Kitszel
2025-12-04 13:21 ` [Intel-wired-lan] " Simon Horman
2025-12-04 13:21 ` Simon Horman
2025-12-04 16:20 ` [Intel-wired-lan] " Jakub Kicinski
2025-12-04 16:20 ` Jakub Kicinski
2025-12-04 16:20 ` Jakub Kicinski [this message]
2025-12-04 16:20 ` Jakub Kicinski
2025-12-10 7:12 ` [Intel-wired-lan] " Jakub Kicinski
2025-12-10 7:12 ` Jakub Kicinski
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=20251204082049.1ecfd15f@kernel.org \
--to=kuba@kernel.org \
--cc=adrian.pielech@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=krzysztof.galazka@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.