From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinj@marvell.com>, lironh@marvell.com
Cc: dev@dpdk.org, david.marchand@redhat.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v5 0/5] remove octeontx2 drivers
Date: Wed, 12 Jan 2022 15:37:29 +0100 [thread overview]
Message-ID: <1693052.X513TT2pbd@thomas> (raw)
In-Reply-To: <20211211090435.2889574-1-jerinj@marvell.com>
> Jerin Jacob (1):
> drivers: remove octeontx2 drivers
>
> Liron Himi (4):
> common/cnxk: add REE HW definitions
> common/cnxk: add REE mbox definitions
> common/cnxk: add REE support
> regex/cn9k: use cnxk infrastructure
Applied, thanks.
next prev parent reply other threads:[~2022-01-12 14:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 6:23 [dpdk-dev] [PATCH] common/cnxk: add REE support lironh
2021-10-28 9:30 ` Jerin Jacob
2021-11-23 19:13 ` [PATCH v2 0/5] regex/cn9k: use cnxk infrastructure lironh
2021-11-23 19:13 ` [PATCH v2 1/5] common/cnxk: add REE HW definitions lironh
2021-11-23 19:13 ` [PATCH v2 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-23 19:13 ` [PATCH v2 3/5] common/cnxk: add REE support lironh
2021-11-23 19:13 ` [PATCH v2 4/5] common/cnxk: link REE support to ROC files lironh
2021-11-23 19:13 ` [PATCH v2 5/5] regex/cn9k: use cnxk infrastructure lironh
[not found] ` <20211123193835.20601-1-robot@bytheb.org>
2021-11-28 20:17 ` [EXT] |FAILURE| pw104631 " Liron Himi
2021-11-28 20:37 ` Thomas Monjalon
2021-11-29 9:55 ` Liron Himi
2021-11-29 10:10 ` Thomas Monjalon
2021-11-29 19:47 ` [PATCH v2 0/5] " lironh
2021-11-29 19:47 ` [PATCH v3 " lironh
2021-11-29 19:47 ` [PATCH v3 1/5] common/cnxk: add REE HW definitions lironh
2021-12-07 18:31 ` [PATCH v4 0/4] regex/cn9k: use cnxk infrastructure lironh
2021-12-07 18:31 ` [PATCH v4 1/4] common/cnxk: add REE HW definitions lironh
2021-12-07 18:31 ` [PATCH v4 2/4] common/cnxk: add REE mbox definitions lironh
2021-12-07 18:31 ` [PATCH v4 3/4] common/cnxk: add REE support lironh
2021-12-07 18:31 ` [PATCH v4 4/4] regex/cn9k: use cnxk infrastructure lironh
2021-12-08 9:14 ` [PATCH v4 0/4] " Jerin Jacob
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 0/5] remove octeontx2 drivers jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 1/5] common/cnxk: add REE HW definitions jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 2/5] common/cnxk: add REE mbox definitions jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 3/5] common/cnxk: add REE support jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 4/5] regex/cn9k: use cnxk infrastructure jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 5/5] drivers: remove octeontx2 drivers jerinj
2021-12-14 8:57 ` Ruifeng Wang
2022-01-12 14:37 ` Thomas Monjalon [this message]
2021-11-29 19:47 ` [PATCH v3 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-29 19:47 ` [PATCH v3 3/5] common/cnxk: add REE support lironh
2021-11-29 19:47 ` [PATCH v3 4/5] common/cnxk: link REE support to ROC files lironh
2021-11-29 19:47 ` [PATCH v3 5/5] regex/cn9k: use cnxk infrastructure lironh
2021-11-29 19:49 ` [PATCH v3 0/5] " lironh
2021-11-29 19:49 ` [PATCH v3 1/5] common/cnxk: add REE HW definitions lironh
2021-11-29 19:49 ` [PATCH v3 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-29 19:49 ` [PATCH v3 3/5] common/cnxk: add REE support lironh
2021-11-29 19:49 ` [PATCH v3 4/5] common/cnxk: link REE support to ROC files lironh
2021-11-29 19:49 ` [PATCH v3 5/5] regex/cn9k: use cnxk infrastructure lironh
2021-11-29 19:59 ` [PATCH v3 0/5] " lironh
2021-11-29 19:59 ` [PATCH v3 1/5] common/cnxk: add REE HW definitions lironh
2021-11-29 19:59 ` [PATCH v3 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-29 19:59 ` [PATCH v3 3/5] common/cnxk: add REE support lironh
2021-11-29 19:59 ` [PATCH v3 4/5] common/cnxk: link REE support to ROC files lironh
2021-12-06 5:07 ` Jerin Jacob
2021-12-06 6:54 ` [EXT] " Liron Himi
2021-12-06 8:08 ` Jerin Jacob
2021-11-29 19:59 ` [PATCH v3 5/5] regex/cn9k: use cnxk infrastructure lironh
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=1693052.X513TT2pbd@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=lironh@marvell.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).