From: "Daniel Xu" <dxu@dxuuu.xyz>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "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:58:30 -0800 [thread overview]
Message-ID: <718b7af5-25f1-4a22-85a8-193b53db499a@app.fastmail.com> (raw)
In-Reply-To: <20241112174434.011bd0f6@kernel.org>
Hi Jakub,
On Tue, Nov 12, 2024, at 5:44 PM, Jakub Kicinski wrote:
> On Mon, 11 Nov 2024 19:23:31 -0700 Daniel Xu wrote:
>> Extend the rss_ctx test suite to test that an ntuple action that
>> redirects to an RSS context contains that information in `ethtool -n`.
>> Otherwise the output from ethtool is highly deceiving. This test helps
>> ensure drivers are compliant with the API.
>
> Looks like it doesn't apply, please base the v3 on net rather than
> net-next, I'll deal with the merge.
Sorry about that. Will think on how to make my workflow not involve
manually retyping patches between different machines...
prev parent reply other threads:[~2024-11-13 1:58 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 " 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
2024-11-13 1:44 ` Jakub Kicinski
2024-11-13 1:58 ` Daniel Xu [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=718b7af5-25f1-4a22-85a8-193b53db499a@app.fastmail.com \
--to=dxu@dxuuu.xyz \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®