DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com
Subject: Re: [PATCH 00/17] NFP bugfix
Date: Mon, 8 Jul 2024 00:58:18 +0100	[thread overview]
Message-ID: <3f47d7e1-cf40-4766-b497-b89598861366@amd.com> (raw)
In-Reply-To: <20240624015723.3712898-1-chaoyong.he@corigine.com>

On 6/24/2024 2:57 AM, Chaoyong He wrote:
> This patch series consist a branch of bugfix patches from NFP PMD,
> in order to speed up the review process and avoid send them out one
> by one.
> 
> Chaoyong He (4):
>   net/nfp: fix coredump caused by firmware abnormal cleanup
>   net/nfp: forbid offload flow rules with empty action list
>   net/nfp: remove redundancy function call
>   net/nfp: fix null pointer dereferences
> 
> Long Wu (6):
>   net/nfp: fix flow rule match data problem
>   net/nfp: fix flow rule action data problem
>   net/nfp: enlarge the flow rules limitation
>   net/nfp: enlarge flow hash table size
>   net/nfp: fix flow position index problem
>   net/nfp: fix port action core dump
> 
> Peng Zhang (3):
>   doc: update the metadata description section
>   net/nfp: remove the unneeded logic
>   net/nfp: adapts the reverse sequence card
> 
> Zerun Fu (4):
>   net/nfp: refactor speed configuration logic
>   net/nfp: refactor device speed update logic
>   net/nfp: fix link status display problem
>   net/nfp: fix getting firmware version
>

Except from 17/17,

Series applied to dpdk-next-net/main, thanks.

      parent reply	other threads:[~2024-07-07 23:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24  1:57 Chaoyong He
2024-06-24  1:57 ` [PATCH 01/17] net/nfp: refactor speed configuration logic Chaoyong He
2024-06-24  1:57 ` [PATCH 02/17] net/nfp: refactor device speed update logic Chaoyong He
2024-06-24  1:57 ` [PATCH 03/17] net/nfp: fix link status display problem Chaoyong He
2024-06-24  1:57 ` [PATCH 04/17] net/nfp: fix coredump caused by firmware abnormal cleanup Chaoyong He
2024-06-24  1:57 ` [PATCH 05/17] net/nfp: forbid offload flow rules with empty action list Chaoyong He
2024-06-24  1:57 ` [PATCH 06/17] net/nfp: remove redundancy function call Chaoyong He
2024-06-24  1:57 ` [PATCH 07/17] net/nfp: fix flow rule match data problem Chaoyong He
2024-06-24  1:57 ` [PATCH 08/17] net/nfp: fix flow rule action " Chaoyong He
2024-06-24  1:57 ` [PATCH 09/17] net/nfp: enlarge the flow rules limitation Chaoyong He
2024-06-24  1:57 ` [PATCH 10/17] net/nfp: enlarge flow hash table size Chaoyong He
2024-06-24  1:57 ` [PATCH 11/17] net/nfp: fix flow position index problem Chaoyong He
2024-06-24  1:57 ` [PATCH 12/17] net/nfp: fix getting firmware version Chaoyong He
2024-06-24  1:57 ` [PATCH 13/17] doc: update the metadata description section Chaoyong He
2024-06-24  1:57 ` [PATCH 14/17] net/nfp: remove the unneeded logic Chaoyong He
2024-06-24  1:57 ` [PATCH 15/17] net/nfp: adapts the reverse sequence card Chaoyong He
2024-06-24  1:57 ` [PATCH 16/17] net/nfp: fix null pointer dereferences Chaoyong He
2024-06-24  1:57 ` [PATCH 17/17] net/nfp: fix port action core dump Chaoyong He
2024-07-07 23:57   ` Ferruh Yigit
2024-07-08  3:12   ` [PATCH v2] " Chaoyong He
2024-07-08 16:00     ` Ferruh Yigit
2024-07-07 23:58 ` Ferruh Yigit [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=3f47d7e1-cf40-4766-b497-b89598861366@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=oss-drivers@corigine.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).