From: Jakub Kicinski <kuba@kernel.org>
To: Joe Damato <joe@dama.to>
Cc: Michael Chan <michael.chan@broadcom.com>,
davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH net 4/4] selftests: drv-net: rss_ctx: test RSS contexts persist after ifdown/up
Date: Thu, 29 Jan 2026 15:58:04 -0800 [thread overview]
Message-ID: <20260129155804.492ca32a@kernel.org> (raw)
In-Reply-To: <aXvA11H0AvNcjaWJ@devvm20253.cco0.facebook.com>
On Thu, 29 Jan 2026 12:19:35 -0800 Joe Damato wrote:
> > .../selftests/drivers/net/hw/rss_ctx.py | 117 +++++++++++++++++-
> > 1 file changed, 116 insertions(+), 1 deletion(-)
>
> I feel like this one might be net-next material since it is a new test and not
> a "Fixes" ?
Quoting documentation:
Co-posting selftests
~~~~~~~~~~~~~~~~~~~~
Selftests should be part of the same series as the code changes.
Specifically for fixes both code change and related test should go into
the same tree (the tests may lack a Fixes tag, which is expected).
Mixing code changes and test changes in a single commit is discouraged.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#co-posting-selftests
next prev parent reply other threads:[~2026-01-29 23:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 6:16 [PATCH net 0/4] bnxt_en: Fix RSS context and ntuple filter issues Michael Chan
2026-01-29 6:16 ` [PATCH net 1/4] bnxt_en: Fix RSS context delete logic Michael Chan
2026-01-29 6:16 ` [PATCH net 2/4] bnxt_en: Don't overload fw_vnic_id for RSS context's filters Michael Chan
2026-01-29 6:16 ` [PATCH net 3/4] bnxt_en: Fix deleting of Ntuple filters Michael Chan
2026-01-29 6:16 ` [PATCH net 4/4] selftests: drv-net: rss_ctx: test RSS contexts persist after ifdown/up Michael Chan
2026-01-29 20:19 ` Joe Damato
2026-01-29 23:58 ` Jakub Kicinski [this message]
2026-01-30 2:03 ` Jakub Kicinski
2026-01-30 3:52 ` Pavan Chebbi
2026-01-30 5:24 ` Pavan Chebbi
2026-01-30 16:09 ` Jakub Kicinski
2026-02-04 16:15 ` Pavan Chebbi
2026-02-05 2:09 ` Jakub Kicinski
2026-02-05 5:41 ` Pavan Chebbi
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=20260129155804.492ca32a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joe@dama.to \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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