From: Thomas Monjalon <thomas@monjalon.net>
To: Xueming Li <xuemingl@nvidia.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH] doc: deprecation notice to add new hash function
Date: Fri, 28 Jul 2023 17:10:05 +0200 [thread overview]
Message-ID: <2763952.BEx9A2HvPv@thomas> (raw)
In-Reply-To: <20230524074915.72538255@hermes.local>
24/05/2023 16:49, Stephen Hemminger:
> On Wed, 24 May 2023 19:38:27 +0800
> Xueming Li <xuemingl@nvidia.com> wrote:
>
> > +
> > +* ethdev: The enum ``rte_eth_hash_function`` will be extended to add
> > + new subtype value ``RTE_ETH_HASH_FUNCTION_SYMMETRIC_TOEPLITZ_SORT`` in
> > + DPDK 23.11.
>
> Simple new additions like this don't need to clutter the deprecation
> part of the release notes. This is for changes which would break applications.
Marking this patch as superseded.
My patch is mentioning such case: adding an enum field.
https://patches.dpdk.org/project/dpdk/patch/20230728142946.1201459-1-thomas@monjalon.net/
next prev parent reply other threads:[~2023-07-28 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 11:38 [PATCH] doc: deprecation notice to add new hash function Xueming Li
2023-05-24 12:50 ` Ori Kam
2023-05-24 14:49 ` Stephen Hemminger
2023-07-28 15:10 ` Thomas Monjalon [this message]
2023-08-07 11:54 ` [PATCH] ethdev: add new symmetric " Xueming Li
2023-08-07 12:33 ` Ori Kam
2023-08-07 22:32 ` Ivan Malov
2023-08-08 1:43 ` fengchengwen
2023-08-09 12:00 ` Xueming(Steven) Li
2023-08-27 8:17 ` [PATCH v2 1/2] " Xueming Li
2023-08-30 6:55 ` Ori Kam
2023-09-21 15:49 ` Ferruh Yigit
2023-09-22 6:57 ` Xueming(Steven) Li
2023-08-30 7:50 ` lihuisong (C)
2023-08-30 8:38 ` Xueming(Steven) Li
2023-08-30 12:42 ` lihuisong (C)
2023-08-30 13:09 ` Xueming(Steven) Li
2023-08-31 1:23 ` lihuisong (C)
2023-08-31 6:25 ` Xueming(Steven) Li
2023-08-31 11:29 ` lihuisong (C)
2023-08-27 8:17 ` [PATCH v2 2/2] net/mlx5: support new RSS " Xueming Li
2023-10-29 15:53 ` Ori Kam
2023-10-30 17:08 ` Raslan Darawsheh
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=2763952.BEx9A2HvPv@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=xuemingl@nvidia.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.