patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>,
	"Loftus, Ciara" <ciara.loftus@intel.com>,
	Luca Boccassi <luca.boccassi@gmail.com>,
	"Xueming(Steven) Li" <xuemingl@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH v3 10/15] net/ice: remove unsupported Rx offload
Date: Mon, 15 Sep 2025 10:39:10 +0100	[thread overview]
Message-ID: <d9b7790c-1a71-4438-a9ad-6efc3cf51e7b@redhat.com> (raw)
In-Reply-To: <CAJFAV8xp1Bckbudei4JFAFAacFYi8wTd50TnWXT0BqFSOMixSg@mail.gmail.com>

On 15/09/2025 09:59, David Marchand wrote:
> On Mon, 15 Sept 2025 at 10:45, Loftus, Ciara <ciara.loftus@intel.com> wrote:
>>
>>>
>>> On Mon, 18 Aug 2025 at 13:00, Ciara Loftus <ciara.loftus@intel.com> wrote:
>>>>
>>>> The offload RTE_ETH_RX_OFFLOAD_SCTP_CKSUM is not supported in the ice
>>>> driver so remove the one erroneous use of it.
>>>>
>>>> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
>>>> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>>>
>>> I just noticed this fix in main.
>>> Fixes: 808a17b3c1e6 ("net/ice: add Rx AVX512 offload path")
>>>
>>> This looks like something worth fixing in LTS.
>>> Was it intentional not marking it for backport?
>>
>> Apologies, it was not intentional not marking it for backport. I should have added that.
> 
> The fault is not yours.
> Let's blame the reviewer instead ;-).
> 
> 
>> Shall I submit a new patch to be backported or can this one be used?
> 
> It is ok.
> Just, the scripts won't catch this fix, so let's ping people.
> @LTS maintainers, fyi.
> 
> 

Ack for 24.11


      reply	other threads:[~2025-09-15  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250818105914.169732-1-ciara.loftus@intel.com>
     [not found] ` <20250818105914.169732-11-ciara.loftus@intel.com>
     [not found]   ` <CAJFAV8wu3jQh2WAY_aUdS-Y1xFMFFtYrGGh_hgbROmMaEpWcgQ@mail.gmail.com>
     [not found]     ` <DM3PPF7D18F34A18F628B6488BAB7ADD7608E15A@DM3PPF7D18F34A1.namprd11.prod.outlook.com>
2025-09-15  8:59       ` David Marchand
2025-09-15  9:39         ` Kevin Traynor [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=d9b7790c-1a71-4438-a9ad-6efc3cf51e7b@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=luca.boccassi@gmail.com \
    --cc=stable@dpdk.org \
    --cc=xuemingl@nvidia.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).