From: Bruce Richardson <bruce.richardson@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH 0/6] Fix inconsistencies in offload masks
Date: Fri, 25 Sep 2026 14:29:13 +0100 [thread overview]
Message-ID: <arZ3Kd0BJUo1RfE2@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <7453e71e-877b-4446-9122-80d6ac609d86@intel.com>
On Fri, Sep 25, 2026 at 12:50:14PM +0200, Burakov, Anatoly wrote:
> On 9/24/2026 3:13 PM, Ciara Loftus wrote:
> > This series fixes some inconsistencies in the path offload masks and
> > dev_info offload capabilities for the ice, iavf and i40e drivers.
> > The first 3 patches are concerned with fixing the path offload masks.
> > The last 3 patches change how offloads are derived for the dev_info offload
> > capabilities. Instead of defining an explicit list of offloads, reuse the
> > information that is already available in the path offload masks. It should
> > help prevent further inconsistencies in the future.
> >
>
> Series-acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
Series applied to dpdk-next-net-intel
Thanks,
/Bruce
prev parent reply other threads:[~2026-09-25 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:13 [PATCH 0/6] Fix inconsistencies in offload masks Ciara Loftus
2026-09-24 13:13 ` [PATCH 1/6] net/ice: update Rx supported offloads masks Ciara Loftus
2026-09-24 13:13 ` [PATCH 2/6] net/ice: fix Rx vector path offload masks Ciara Loftus
2026-09-24 13:13 ` [PATCH 3/6] net/i40e: drop unimplemented UDP TSO from Tx mask Ciara Loftus
2026-09-24 13:13 ` [PATCH 4/6] net/ice: derive Rx/Tx offload capabilities from path masks Ciara Loftus
2026-09-24 13:13 ` [PATCH 5/6] net/iavf: " Ciara Loftus
2026-09-24 13:13 ` [PATCH 6/6] net/i40e: " Ciara Loftus
2026-09-25 10:50 ` [PATCH 0/6] Fix inconsistencies in offload masks Burakov, Anatoly
2026-09-25 13:29 ` Bruce Richardson [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=arZ3Kd0BJUo1RfE2@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.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