From: Thomas Monjalon <thomas@monjalon.net>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
dev@dpdk.org, "Nicolau, Radu" <radu.nicolau@intel.com>,
"R, Kamalakannan" <kamalakannan.r@intel.com>,
"Suresh Narayane, Harshad" <harshad.suresh.narayane@intel.com>
Subject: Re: [PATCH] doc: postpone deprecation of pipeline legacy API
Date: Fri, 28 Jul 2023 18:02:22 +0200 [thread overview]
Message-ID: <23812310.ouqheUzb2q@thomas> (raw)
In-Reply-To: <DS0PR11MB744276A2576C76EDB0E93598EB3EA@DS0PR11MB7442.namprd11.prod.outlook.com>
> > > Postpone the deprecation of the legacy pipeline, table and port
> > > library API and gradual stabilization of the new API.
> > >
> > > Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> > > ---
> > > doc/guides/rel_notes/deprecation.rst | 21 +++++++++------------
> > > 1 file changed, 9 insertions(+), 12 deletions(-)
> > >
> >
> > No objection to this, though it would be really good to get the new
> > functions stabilized in 23.11 when we lock down the 24 ABI.
> >
>
> Yes, fully agree, let's see if we can make this happen for 23.11
>
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
next prev parent reply other threads:[~2023-07-28 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 15:12 [PATCH] doc: postpone deprecation of pipeline legacy API Cristian Dumitrescu
2023-07-19 16:08 ` Bruce Richardson
2023-07-20 10:37 ` Dumitrescu, Cristian
2023-07-28 16:02 ` Thomas Monjalon [this message]
2023-07-20 6:12 ` Suresh Narayane, Harshad
2023-07-20 8:18 ` Radu Nicolau
2024-10-11 14:32 ` David Marchand
2026-07-24 8:00 ` David Marchand
2026-07-24 16:58 ` Stephen Hemminger
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=23812310.ouqheUzb2q@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=harshad.suresh.narayane@intel.com \
--cc=kamalakannan.r@intel.com \
--cc=radu.nicolau@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.