From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [pull-request] dpdk-next-eventdev - v21.08-rc3
Date: Fri, 30 Jul 2021 11:02:23 +0000 [thread overview]
Message-ID: <BY3PR18MB47857A5D77BE0EFBF5B46310C8EC9@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
The following changes since commit f8c42c53ce744180e1fb4203b2cf976054726360:
net/mlx5: fix meter hierarchy validation with yellow (2021-07-29 22:06:43 +0200)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to 9661f6ac433d3dd84a9fe001a45f3cb0ae612d78:
eventdev: fix event port setup in Tx adapter (2021-07-30 16:25:19 +0530)
----------------------------------------------------------------
Naga Harish K S V (1):
eventdev: fix event port setup in Tx adapter
Pavan Nikhilesh (1):
event/cnxk: fix reading stale Tx queue depth
drivers/event/cnxk/cn9k_worker.h | 3 ++-
lib/eventdev/rte_event_eth_tx_adapter.c | 1 -
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2021-07-30 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 11:02 Jerin Jacob Kollanukkaran [this message]
2021-07-30 15:16 ` Thomas Monjalon
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=BY3PR18MB47857A5D77BE0EFBF5B46310C8EC9@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).