From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 0/2] fix meta data process problem
Date: Tue, 20 Feb 2024 16:14:49 +0800 [thread overview]
Message-ID: <20240220081451.2640526-1-chaoyong.he@corigine.com> (raw)
The Tx function can not check if the meta data process success for
the process function with void return type. This problem exist for
both NFD3 and NFDk logic.
Chaoyong He (2):
net/nfp: fix meta data process problem of NFD3
net/nfp: fix meta data process problem of NFDk
drivers/net/nfp/nfd3/nfp_nfd3_dp.c | 19 +++++++++++++------
drivers/net/nfp/nfdk/nfp_nfdk_dp.c | 27 ++++++++++++++++++---------
2 files changed, 31 insertions(+), 15 deletions(-)
--
2.39.1
next reply other threads:[~2024-02-20 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:14 Chaoyong He [this message]
2024-02-20 8:14 ` [PATCH 1/2] net/nfp: fix meta data process problem of NFD3 Chaoyong He
2024-02-20 8:14 ` [PATCH 2/2] net/nfp: fix meta data process problem of NFDk Chaoyong He
2024-02-21 17:07 ` [PATCH 0/2] fix meta data process problem Ferruh Yigit
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=20240220081451.2640526-1-chaoyong.he@corigine.com \
--to=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).