From: Breno Leitao <leitao@debian.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andre Carvalho <asantostc@gmail.com>,
Shuah Khan <shuah@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] netconsole: selftests: Move netconsole selftests to separate target
Date: Tue, 27 Jan 2026 03:18:00 -0800 [thread overview]
Message-ID: <aXiefXsiKm0mBjKA@gmail.com> (raw)
In-Reply-To: <20260126162800.10d5601d@kernel.org>
On Mon, Jan 26, 2026 at 04:28:00PM -0800, Jakub Kicinski wrote:
> On Mon, 26 Jan 2026 04:10:18 -0800 Breno Leitao wrote:
> >
> > Thanks for the patch. Looking at NIPA, it seems none of the netconsole
> > test run?
> >
> > https://netdev.bots.linux.dev/contest.html?pw-n=0&branch=net-next-2026-01-25--06-00
>
> Do you mean after the patch?
Right. I am looking at the patch entry in patchwork and didn't see the
test run.
https://patchwork.kernel.org/project/netdevbpf/patch/20260124-netcons-selftest-target-v1-1-d3937f44c4c2@gmail.com/
> I'll have to manually add it to some VM config (presumably the SW
> drv-net one).
I didn't know that. I thought it would run automatically, sorry.
> I'll do it after patch is merged. (Remind me if I forget? ;))
Let me know if you want us to do it,
--breno
next prev parent reply other threads:[~2026-01-27 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 18:51 [PATCH net-next] netconsole: selftests: Move netconsole selftests to separate target Andre Carvalho
2026-01-26 12:10 ` Breno Leitao
2026-01-27 0:28 ` Jakub Kicinski
2026-01-27 11:18 ` Breno Leitao [this message]
2026-01-27 18:00 ` Jakub Kicinski
2026-01-27 19:34 ` Andre Carvalho
2026-01-27 11:18 ` Breno Leitao
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=aXiefXsiKm0mBjKA@gmail.com \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.