From: Thomas Monjalon <thomas@monjalon.net>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
dev@dpdk.org, xen-devel@lists.xenproject.org, "Mcnamara,
John" <john.mcnamara@intel.com>,
joao.m.martins@oracle.com, jerin.jacob@caviumnetworks.com,
shahafs@mellanox.com
Subject: Re: [PATCH 5/6] eal: remove xen dom0 support
Date: Tue, 05 Sep 2017 09:31:28 +0200 [thread overview]
Message-ID: <18154944.ikgZCrDS5M@xps> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E36512AFF27@SHSMSX103.ccr.corp.intel.com>
05/09/2017 05:41, Tan, Jianfeng:
> From: Richardson, Bruce
> >
> > Reading the contributors guide section on ABI, specifically
> > http://dpdk.org/doc/guides/contributing/versioning.html#deprecating-an-
> > entire-abi-version
> > it seems like we should collapse down the versions to a single one
> > following the function removal, and also increment the whole library so
> > version.
>
> So for lib/librte_eal/linuxapp/eal/rte_eal_version.map, we should change it in below way?
>
> DPDK_2.1 {
> {APIs in DPDK_2.0 except xen APIs}
> ...
> };
>
> DPDK_16.04 {
> {APIs in DPDK_2.1 except xen APIs}
> ...
> } DPDK_2.1;
No, you don't need to collapse. You can just remove Xen functions.
next prev parent reply other threads:[~2017-09-05 7:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 18:10 [PATCH 0/6] remove xen dom0 support in DPDK Jianfeng Tan
2017-08-30 18:10 ` [PATCH 1/6] example/vhost_xen: remove Jianfeng Tan
2017-09-04 14:14 ` Bruce Richardson
2017-09-04 14:14 ` [dpdk-dev] " Bruce Richardson
2017-08-30 18:10 ` Jianfeng Tan
2017-08-30 18:10 ` [PATCH 2/6] net/xenvirt: remove Jianfeng Tan
2017-09-04 14:25 ` [dpdk-dev] " Bruce Richardson
2017-09-04 14:25 ` Bruce Richardson
2017-09-04 14:50 ` [dpdk-dev] " Bruce Richardson
2017-09-04 14:50 ` Bruce Richardson
2017-08-30 18:10 ` Jianfeng Tan
2017-08-30 18:10 ` [PATCH 3/6] xen: remove xen dependency in app, examples, test Jianfeng Tan
2017-08-30 18:10 ` Jianfeng Tan
2017-09-04 14:24 ` [dpdk-dev] " Bruce Richardson
2017-09-04 14:24 ` Bruce Richardson
2017-09-04 14:51 ` Bruce Richardson
2017-09-04 14:51 ` [dpdk-dev] " Bruce Richardson
2017-08-30 18:10 ` [PATCH 4/6] xen: remove xen dependency in drivers, ether, mempool Jianfeng Tan
2017-09-04 14:51 ` [dpdk-dev] " Bruce Richardson
2017-09-04 14:51 ` Bruce Richardson
2017-08-30 18:10 ` Jianfeng Tan
2017-08-30 18:10 ` [PATCH 5/6] eal: remove xen dom0 support Jianfeng Tan
2017-09-04 14:43 ` Bruce Richardson
2017-09-04 14:49 ` [dpdk-dev] " Bruce Richardson
2017-09-04 14:49 ` Bruce Richardson
2017-09-05 3:41 ` [dpdk-dev] " Tan, Jianfeng
2017-09-05 3:41 ` Tan, Jianfeng
2017-09-05 7:31 ` [dpdk-dev] " Thomas Monjalon
2017-09-05 7:31 ` Thomas Monjalon [this message]
2017-09-05 8:07 ` Tan, Jianfeng
2017-09-05 8:07 ` Tan, Jianfeng
2017-09-05 8:34 ` [dpdk-dev] " Thomas Monjalon
2017-09-05 8:34 ` Thomas Monjalon
2017-09-04 14:43 ` [dpdk-dev] " Bruce Richardson
2017-08-30 18:10 ` [PATCH 6/6] eal: remove API rte_mem_phy2mch Jianfeng Tan
2017-09-04 14:52 ` Bruce Richardson
2017-09-04 14:52 ` [dpdk-dev] " Bruce Richardson
2017-08-31 8:44 ` [PATCH 0/6] remove xen dom0 support in DPDK Wei Liu
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=18154944.ikgZCrDS5M@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianfeng.tan@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=john.mcnamara@intel.com \
--cc=shahafs@mellanox.com \
--cc=xen-devel@lists.xenproject.org \
/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.