netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	"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>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Krzysztof Galazka <krzysztof.galazka@intel.com>
Subject: Re: [ANN] intel's netdev-ci
Date: Thu, 4 Dec 2025 13:21:31 +0000	[thread overview]
Message-ID: <aTGK25rhhwUinDqn@horms.kernel.org> (raw)
In-Reply-To: <a0561c1f-f64e-4d76-b08b-877897d45eae@intel.com>

On Thu, Dec 04, 2025 at 01:59:34PM +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.
> 
> 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/

Thanks, this is very nice to see.

  reply	other threads:[~2025-12-04 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 12:59 [ANN] intel's netdev-ci Przemek Kitszel
2025-12-04 13:21 ` Simon Horman [this message]
2025-12-04 16:20 ` Jakub Kicinski
2025-12-04 16:20   ` 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=aTGK25rhhwUinDqn@horms.kernel.org \
    --to=horms@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=intel-wired-lan@lists.osuosl.org \
    --cc=krzysztof.galazka@intel.com \
    --cc=kuba@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).