From: Jakub Kicinski <kuba@kernel.org>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, cai.huoqing@linux.dev,
netdev@vger.kernel.org, felipe@sipanda.io,
justin.iurman@uliege.be
Subject: Re: [PATCH net-next v2 0/7] drivers: Fix drivers doing TX csum offload with EH
Date: Tue, 2 Jul 2024 18:46:33 -0700 [thread overview]
Message-ID: <20240702184633.1f05673c@kernel.org> (raw)
In-Reply-To: <20240701195507.256374-1-tom@herbertland.com>
On Mon, 1 Jul 2024 12:55:00 -0700 Tom Herbert wrote:
> Testing: The code compiles, but is otherwise untested due to lack of
> NIC hardware. It would be appreciated if someone with access to the
> hardware could test.
Could you pop a script under tools/testing/selftests/drivers/net/
that'd exercise this?
This will hopefully guarantee good coverage soon, due to:
https://netdev.bots.linux.dev/devices.html
next prev parent reply other threads:[~2024-07-03 1:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 19:55 [PATCH net-next v2 0/7] drivers: Fix drivers doing TX csum offload with EH Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 1/7] ipv6: Add ipv6_skip_exthdr_no_rthdr Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 2/7] i40e: Don't do TX csum offload with routing header present Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 3/7] iavf: " Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 4/7] ice: " Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 5/7] idpf: " Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 6/7] hinic: " Tom Herbert
2024-07-01 19:55 ` [PATCH net-next v2 7/7] fm10k: " Tom Herbert
2024-07-02 10:31 ` [PATCH net-next v2 0/7] drivers: Fix drivers doing TX csum offload with EH Przemek Kitszel
2024-07-03 14:20 ` Greenwalt, Paul
[not found] ` <CALx6S35zhg8HAUj9_1=Zm=nV0mzSe-Batdo5qpjz6Zd4G8T17g@mail.gmail.com>
2024-07-03 15:02 ` Przemek Kitszel
2024-07-03 15:56 ` Tom Herbert
2024-07-03 1:46 ` Jakub Kicinski [this message]
2024-07-03 14:39 ` Tom Herbert
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=20240702184633.1f05673c@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=cai.huoqing@linux.dev \
--cc=davem@davemloft.net \
--cc=felipe@sipanda.io \
--cc=jesse.brandeburg@intel.com \
--cc=justin.iurman@uliege.be \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).