From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 6523BA00E6
	for <public@inbox.dpdk.org>; Mon,  5 Aug 2019 17:06:01 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id C1A761B9CD;
	Mon,  5 Aug 2019 17:06:00 +0200 (CEST)
Received: from mail-vs1-f66.google.com (mail-vs1-f66.google.com
 [209.85.217.66]) by dpdk.org (Postfix) with ESMTP id 9A1DD1B9A6
 for <dev@dpdk.org>; Mon,  5 Aug 2019 17:05:58 +0200 (CEST)
Received: by mail-vs1-f66.google.com with SMTP id m8so56233391vsj.0
 for <dev@dpdk.org>; Mon, 05 Aug 2019 08:05:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=ptYwUkHwPYitlapA5fuy2YBRG+uCIQMXAzar9uQTXKY=;
 b=bSv6fk7C4FrcJhKZyTFu4zVvUIjJ9zn1Yhw/SU/V5Toc0/mYsyV0GBzd3AWosUs5Qt
 UZcoddZtBNELew8quYR1jz0CfFYk01tuU6y08J3P1pC2DN0KA69GdVp2TF3GOFIStwk6
 Rw//zmTSa6yb90PQLeBTktmxz4BCFO7bo2TL+iFgq+NfTi/gohT4SJ7mSOGqro+Adrb/
 W2+u6s3wWOLJGaEAX4KUYm7okt2eH9ghLc4pKbhTqBH2mFi6imeL24tc6qO4GYGVAKjD
 001eGjKwPaktjY8rA8+Bulrw5dM+uM72hoTm4In8555myGT/HSxoZIxATf/G59ivuSMC
 FVIQ==
X-Gm-Message-State: APjAAAUwtFDgyX2xgSMOtJdbJGgl6txFwQ8ll9q5iavxUELBLv4cVinW
 c+XD8En+FN7KQZDkJiQVLG3VFPO1H6tzcuf4hA+kxg==
X-Google-Smtp-Source: APXvYqxaIBRMmPoVMrRtsE5z6MxOCupZMNhNkmhasbtwt9pHOSfzMJTJdJy7Ztj2fDD/wuvBx8qlqHXBa8KFQQDvCV0=
X-Received: by 2002:a67:e9ca:: with SMTP id q10mr63481840vso.105.1565017557905; 
 Mon, 05 Aug 2019 08:05:57 -0700 (PDT)
MIME-Version: 1.0
References: <1564752563-11850-1-git-send-email-david.marchand@redhat.com>
 <1667146.ajMsIp94DY@xps>
In-Reply-To: <1667146.ajMsIp94DY@xps>
From: David Marchand <david.marchand@redhat.com>
Date: Mon, 5 Aug 2019 17:05:46 +0200
Message-ID: <CAJFAV8w3H9=v53NJ4i1c3wyLQHzc6h9itPaP5HcTHqaXHmnaMg@mail.gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>, "Burakov, Anatoly" <anatoly.burakov@intel.com>, 
 Bruce Richardson <bruce.richardson@intel.com>,
 Ray Kinsella <ray.kinsella@intel.com>, 
 "Traynor, Kevin" <ktraynor@redhat.com>,
 Stephen Hemminger <stephen@networkplumber.org>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [dpdk-dev] [PATCH] doc: announce malloc virt2phys symbol removal
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
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
Sender: "dev" <dev-bounces@dpdk.org>

On Mon, Aug 5, 2019 at 4:39 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 02/08/2019 15:29, David Marchand:
> > This symbol has been deprecated for quite some time.
> > Let's drop it in the next release.
> > ---
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > +* eal: The ``rte_malloc_virt2phy`` function has been deprecated and replaced
> > +  by ``rte_malloc_virt2iova`` since v17.11 and will be removed in DPDK 19.11.
>
> For this patch and another one about removing rte_cpu_check_supported(),
> I have a general comment on the date of removal.
>
> As was stated recently in the contribution guide:
>         http://git.dpdk.org/dpdk/commit/?id=7abe4a24cc
>         "Deprecated APIs are removed completely just after the next LTS."
>
> The idea behind this policy is to avoid removals during LTS releases,
> in order to have at least one release before X.11 LTS for end users
> to prepare replacing the usage of the removed API.
>
> Does it make sense to postpone any API removal after 19.11?

Those symbols have been marked as deprecated for a long time.
Users had to either disable Werror or they actually migrated to the new apis.
If they chose the lazy way of not migrating to the new apis, I suspect
they forgot about it and/or they won't look at the release notes.


I don't particularly have a problem with waiting for 20.02, those are
easy to remove anyway.

-- 
David Marchand