From: Jerin Jacob <jerinjacobk@gmail.com>
To: jerinj@marvell.com
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Liron Himi <lironh@marvell.com>,
david.marchand@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 2/2] common/cnxk: fix direct rte symbol usage in REE
Date: Thu, 5 Oct 2023 19:47:24 +0530 [thread overview]
Message-ID: <CALBAE1OFcqwTRAdQBZ0RC4Vvsqxi=kyS0Rqm2iH-UOUREgt_Rg@mail.gmail.com> (raw)
In-Reply-To: <20231004122432.3255418-2-jerinj@marvell.com>
On Wed, Oct 4, 2023 at 5:55 PM <jerinj@marvell.com> wrote:
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> The common code is shared between different driver environments,
> introduce missing plt_ abstractions of missing rte_ symbols and
> use plt symbols to avoid changing roc_* files.
>
> Fixes: c88d3638c7fc ("common/cnxk: support REE")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Series applied to dpdk-next-net-mrvl/for-next-net. Thanks
prev parent reply other threads:[~2023-10-05 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:39 [dpdk-dev] [PATCH] common/cnxk: fix direct rte symbol usage jerinj
2023-10-04 4:39 ` Nithin Dabilpuram
2023-10-04 6:03 ` David Marchand
2023-10-04 6:41 ` Jerin Jacob
2023-10-04 7:36 ` David Marchand
2023-10-04 7:47 ` Jerin Jacob
[not found] ` <20231004122432.3255418-1-jerinj@marvell.com>
2023-10-04 12:24 ` [dpdk-dev] [PATCH v2 2/2] common/cnxk: fix direct rte symbol usage in REE jerinj
2023-10-05 14:17 ` Jerin Jacob [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='CALBAE1OFcqwTRAdQBZ0RC4Vvsqxi=kyS0Rqm2iH-UOUREgt_Rg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=lironh@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).