patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
To: Chaoyong He <chaoyong.he@corigine.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "oss-drivers@corigine.com" <oss-drivers@corigine.com>
Subject: Re: [PATCH 23.11 0/2] backport NFP patches to DPDK 23.11.2
Date: Wed, 21 Aug 2024 08:56:03 +0000	[thread overview]
Message-ID: <CH3PR12MB8658AA8E852D54E490C40F10A18E2@CH3PR12MB8658.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240814025038.1698473-1-chaoyong.he@corigine.com>

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Hi Chaoyong,

Thanks for the backporting, patch sent to release candidate queue.

Best Regards,
Xueming
________________________________
From: Chaoyong He <chaoyong.he@corigine.com>
Sent: Wednesday, August 14, 2024 10:50 AM
To: stable@dpdk.org <stable@dpdk.org>
Cc: oss-drivers@corigine.com <oss-drivers@corigine.com>; Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 23.11 0/2] backport NFP patches to DPDK 23.11.2

This patch series aims to backport 2 patches to DPDK 23.11.2:
3a64e190bc  Chaoyong He      net/nfp: fix firmware abnormal cleanup
78bbab1628  Chaoyong He      net/nfp: forbid offload flow rules with empty action list

Chaoyong He (2):
  net/nfp: fix firmware abnormal cleanup
  net/nfp: forbid offload flow rules with empty action list

 drivers/net/nfp/nfp_ethdev.c | 6 ++++--
 drivers/net/nfp/nfp_flow.c   | 5 +++++
 2 files changed, 9 insertions(+), 2 deletions(-)

--
2.39.1


[-- Attachment #2: Type: text/html, Size: 2767 bytes --]

      parent reply	other threads:[~2024-08-21  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14  2:50 Chaoyong He
2024-08-14  2:50 ` [PATCH 23.11 1/2] net/nfp: fix firmware abnormal cleanup Chaoyong He
2024-08-14  2:50 ` [PATCH 23.11 2/2] net/nfp: forbid offload flow rules with empty action list Chaoyong He
2024-08-21  8:56 ` Xueming Li [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=CH3PR12MB8658AA8E852D54E490C40F10A18E2@CH3PR12MB8658.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=chaoyong.he@corigine.com \
    --cc=oss-drivers@corigine.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).