From: Jakub Kicinski <kuba@kernel.org>
To: Sheena Mohan <sheenamo@google.com>
Cc: Harshitha Ramamurthy <hramamurthy@google.com>,
netdev@vger.kernel.org, Willem de Bruijn <willemb@google.com>
Subject: Re: [TEST] google runner needs nested cases
Date: Tue, 28 Jul 2026 16:22:51 -0700 [thread overview]
Message-ID: <20260728162251.24efb0ce@kernel.org> (raw)
In-Reply-To: <CADWJPTuet6HTd7V104+MmgaS0EO=ZcLu=FiZs_c_CtX231w1cQ@mail.gmail.com>
On Tue, 28 Jul 2026 15:38:56 -0700 Sheena Mohan wrote:
> On Tue, Jul 28, 2026 at 3:13 PM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Tue, 28 Jul 2026 10:07:15 -0700 Sheena Mohan wrote:
> > > The recent updates have been merged, and the tests should now report
> > > sub-case results.
> > > Please let us know if any further improvements are needed.
> >
> > Looks good, thanks!
> >
> > I'm still waiting on the device node, but I assume we're stacking that
> > separately.
> Yes, we are tracking that separately. I will share an update on
> devlink support once the patches are submitted for upstream review.
To be clear -- it's not required to be real devlink.
The format has to be like devlink (JSON keys).
For QEMU virtio for example we have a two liner
bash script in NIPA:
qver=$(qemu-system-x86_64 --version | head -1)
echo '{"driver":"virtio_net","versions":{"fixed":{},"stored":{},"running":{"fw":"'"$qver"'"}}}'
https://github.com/linux-netdev/nipa/blob/main/contest/scripts/vm-virtio-dev-info.sh
Of course real devlink reporting is better because
it may also help users correlate problems in production.
prev parent reply other threads:[~2026-07-28 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 13:38 [TEST] google runner needs nested cases Jakub Kicinski
2026-07-23 17:14 ` Sheena Mohan
2026-07-23 17:36 ` Jakub Kicinski
2026-07-28 17:07 ` Sheena Mohan
2026-07-28 22:13 ` Jakub Kicinski
2026-07-28 22:38 ` Sheena Mohan
2026-07-28 23:22 ` Jakub Kicinski [this message]
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=20260728162251.24efb0ce@kernel.org \
--to=kuba@kernel.org \
--cc=hramamurthy@google.com \
--cc=netdev@vger.kernel.org \
--cc=sheenamo@google.com \
--cc=willemb@google.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