From: Nithin Dabilpuram <nithind1988@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, ndabilpuram@marvell.com,
kirankumark@marvell.com, zhirun.yan@intel.com, dev@dpdk.org
Subject: Re: [PATCH] doc: deprecate graph data structures
Date: Tue, 19 Mar 2024 10:51:03 +0530 [thread overview]
Message-ID: <CAMuDWKT+ph8J+TJ=VPNJeU1dL+Ara0Wb1gS6pPauNtrfeo6_hQ@mail.gmail.com> (raw)
In-Reply-To: <20240221161319.7054-1-pbhagavatula@marvell.com>
Acked-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
On Wed, Feb 21, 2024 at 9:50 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Deprecate rte_node, rte_node_register and rte_graph_cluster_node_stats
> structures as will be extended to include node specific error counters
> and error description.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 10630ba255..b3dfd06ed6 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -142,3 +142,8 @@ Deprecation Notices
> will be deprecated and subsequently removed in DPDK 24.11 release.
> Before this, the new port library API (functions rte_swx_port_*)
> will gradually transition from experimental to stable status.
> +
> +* graph: The graph library data structures will be modified to
> + support node specific errors, the structures ``rte_node``,
> + ``rte_node_register`` and ``rte_graph_cluster_node_stats`` will be
> + extended to include node error counters and error description.
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-03-19 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 16:13 pbhagavatula
2024-03-19 3:22 ` Jerin Jacob
2024-03-19 15:50 ` Stephen Hemminger
2024-03-20 7:29 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2024-03-19 5:21 ` Nithin Dabilpuram [this message]
2024-03-20 3:07 ` Yan, Zhirun
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='CAMuDWKT+ph8J+TJ=VPNJeU1dL+Ara0Wb1gS6pPauNtrfeo6_hQ@mail.gmail.com' \
--to=nithind1988@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=zhirun.yan@intel.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).