From: Jakub Kicinski <kuba@kernel.org>
To: "Daniel Xu" <dxu@dxuuu.xyz>
Cc: "Edward Cree" <ecree.xilinx@gmail.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Eric Dumazet" <edumazet@google.com>,
"David Miller" <davem@davemloft.net>,
"Shuah Khan" <shuah@kernel.org>,
andrew+netdev@lunn.ch, "Michael Chan" <michael.chan@broadcom.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Pavan Chebbi" <pavan.chebbi@broadcom.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Kernel Team" <kernel-team@meta.com>
Subject: Re: [PATCH net v2 2/2] selftests: drv-net: rss_ctx: Add test for ntuple rule
Date: Tue, 12 Nov 2024 17:59:47 -0800 [thread overview]
Message-ID: <20241112175947.4c308ba1@kernel.org> (raw)
In-Reply-To: <d5b21f01-0f19-4580-bb7a-829d46ee7dcb@app.fastmail.com>
On Tue, 12 Nov 2024 17:51:50 -0800 Daniel Xu wrote:
> > This won't match the output from your ethtool patch, because that
> > removes the colon. Probably want to wait until the patch is
> > finalised and then write a regex that matches both versions.
>
> Argh, I meant to have wildcards here. But yeah, makes sense, will wait
> until the other patch is finalized.
Keep in mind Michal scans ethtool patches once every week or two,
so there may be a bit of a delay there.
next prev parent reply other threads:[~2024-11-13 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 2:23 [PATCH net v2 0/2] bnxt: Fix failure to report RSS context in ntuple rule Daniel Xu
2024-11-12 2:23 ` [PATCH net v2 1/2] bnxt_en: ethtool: Supply ntuple rss context action Daniel Xu
2024-11-12 2:23 ` [PATCH net v2 2/2] selftests: drv-net: rss_ctx: Add test for ntuple rule Daniel Xu
2024-11-12 11:10 ` Edward Cree
2024-11-13 1:51 ` Daniel Xu
2024-11-13 1:59 ` Jakub Kicinski [this message]
2024-11-13 1:44 ` Jakub Kicinski
2024-11-13 1:58 ` Daniel Xu
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=20241112175947.4c308ba1@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dxu@dxuuu.xyz \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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.