From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id CABDD42B8E;
	Wed, 24 May 2023 16:49:19 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id B86C940156;
	Wed, 24 May 2023 16:49:19 +0200 (CEST)
Received: from mail-pf1-f172.google.com (mail-pf1-f172.google.com
 [209.85.210.172])
 by mails.dpdk.org (Postfix) with ESMTP id 0DE19400EF
 for <dev@dpdk.org>; Wed, 24 May 2023 16:49:18 +0200 (CEST)
Received: by mail-pf1-f172.google.com with SMTP id
 d2e1a72fcca58-64d30ab1ef2so765962b3a.2
 for <dev@dpdk.org>; Wed, 24 May 2023 07:49:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1684939758;
 x=1687531758; 
 h=content-transfer-encoding:mime-version:references:in-reply-to
 :message-id:subject:cc:to:from:date:from:to:cc:subject:date
 :message-id:reply-to;
 bh=yQZtBPue4gDHb5YkdXWwrRxnM4KUc122AkQq1Xb7Cjg=;
 b=oCc3JdlSx1R/QEsicsFtzklox8qug7JTC3niFhg6+EQ8UUW7GdOPhaMYrfUmlZ/bNm
 ZLlvxCUekfzxb0xxrgbFmJn40dy1zr9SgyPSBn9YLviLDIlDnpZgE0cgN8s9hxILZ9su
 tMQYs9I0h/EbUlU2CSkot9qLHa/WlQShsIA1XHi+ofjBxnl7mgfPpDVbwGwwCLURWAe2
 eBg7j3Hx1at1qmRLy6qqK+w1IbB2Ck9TUX79t4QvYo7MYA3zHMAFpN0vOfdmT1okM475
 b1/J7goFFWwW6c9B8IoclS8VpJFacEHNMPh9w5zITGDsNwIMh9DBiliUEbEfecj7NkPD
 4D0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1684939758; x=1687531758;
 h=content-transfer-encoding:mime-version:references:in-reply-to
 :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=yQZtBPue4gDHb5YkdXWwrRxnM4KUc122AkQq1Xb7Cjg=;
 b=hLArHEQZX6OKOIB99hJCmO6GMXF2AFVWLJTUzMhiZP8IGtPMVs2WyM1o2E2kCWyDoq
 mX4uL3q6VuvPNSKgjTONwl2GRlSIFqhajqLWkxGEbKQekGd12ZGmLpt+fXOVMfZQXBGG
 ivphlUNppwZ2mrBC8fysic6ZrHzGcIIBoNAJdcDajRV1YE0JRQerlN4lQQS3kfI+bbrK
 ebtddUH3pVSWUj87rMEHOkZANJDSauJmbymcDilQgJgHIMSyLZ7vLSBKKtXtYGY+KM3x
 2PfaOiobN8ziYGvM3No3EFPCrq8u3EYD0iDfan8iId81KaTpdVz9ntJxzphwwCH5j0Rl
 nB7Q==
X-Gm-Message-State: AC+VfDwKsp7auEu4SLG6AX7XWwPZ7/fzPyOjaN6EOKOlC3XTXRh8QXsm
 tdb83zDfNCmayIgbQsdMVmbldw==
X-Google-Smtp-Source: ACHHUZ7oofzFxb7FrM2w8erN8ZBZSUqj8+LMG6VIHpdxY5CLahKBGD7PceUS7YEwmpRrCbwX0h1aEw==
X-Received: by 2002:a05:6a00:13a9:b0:63d:2f13:200 with SMTP id
 t41-20020a056a0013a900b0063d2f130200mr3394784pfg.16.1684939758119; 
 Wed, 24 May 2023 07:49:18 -0700 (PDT)
Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218])
 by smtp.gmail.com with ESMTPSA id
 u19-20020a62ed13000000b006439b7f755bsm547438pfh.98.2023.05.24.07.49.17
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Wed, 24 May 2023 07:49:17 -0700 (PDT)
Date: Wed, 24 May 2023 07:49:15 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Xueming Li <xuemingl@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>, <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH] doc: deprecation notice to add new hash function
Message-ID: <20230524074915.72538255@hermes.local>
In-Reply-To: <20230524113827.7351-1-xuemingl@nvidia.com>
References: <20230524113827.7351-1-xuemingl@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

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.