From: Stephen Hemminger <stephen@networkplumber.org>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: pbhagavatula@marvell.com, 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 08:50:09 -0700 [thread overview]
Message-ID: <20240319085009.2638411a@hermes.local> (raw)
In-Reply-To: <CALBAE1O7axMEoEv4tgWx+cbDR-QOaopwsBx2WOGXpObpoAf4yg@mail.gmail.com>
On Tue, 19 Mar 2024 08:52:13 +0530
Jerin Jacob <jerinjacobk@gmail.com> wrote:
> On Wed, Feb 21, 2024 at 9:43 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>
>
> Implementation patches for 24.11 at
> https://patches.dpdk.org/project/dpdk/list/?series=31181.
> The deprecation notice looks good to me.
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Can more of the internals be private to the library to avoid future changes.
next prev parent reply other threads:[~2024-03-19 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 16:13 [PATCH] doc: deprecate graph data structures pbhagavatula
2024-03-19 3:22 ` Jerin Jacob
2024-03-19 15:50 ` Stephen Hemminger [this message]
2024-03-20 7:29 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2024-03-19 5:21 ` Nithin Dabilpuram
2024-03-20 3:07 ` Yan, Zhirun
2024-07-18 12:36 ` Pavan Nikhilesh Bhagavatula
2024-07-31 12:22 ` 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=20240319085009.2638411a@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.