From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
yipeng1.wang@intel.com, pablo.de.lara.guarch@intel.com
Subject: [dpdk-dev] [PATCH 6/6] doc: remove internal libs from release notes
Date: Mon, 15 Oct 2018 15:50:57 +0100 [thread overview]
Message-ID: <20181015145057.37864-6-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20181015145057.37864-1-ferruh.yigit@intel.com>
These libraries has exported functions but the target of those functions
are not user but other libraries.
The version of these libraries doesn't mean much to the user so can be
dropped from release notes.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Indeed this is more a question, should we keep them or remove them?
---
doc/guides/rel_notes/release_18_11.rst | 7 -------
1 file changed, 7 deletions(-)
diff --git a/doc/guides/rel_notes/release_18_11.rst b/doc/guides/rel_notes/release_18_11.rst
index 03f73484e..8b755a7e9 100644
--- a/doc/guides/rel_notes/release_18_11.rst
+++ b/doc/guides/rel_notes/release_18_11.rst
@@ -291,12 +291,6 @@ The libraries prepended with a plus sign were incremented in this version.
librte_bbdev.so.1
librte_bitratestats.so.2
librte_bpf.so.1
- + librte_bus_dpaa.so.2
- + librte_bus_fslmc.so.2
- + librte_bus_ifpga.so.2
- + librte_bus_pci.so.2
- + librte_bus_vdev.so.2
- + librte_bus_vmbus.so.2
librte_cfgfile.so.2
librte_cmdline.so.2
librte_compressdev.so.1
@@ -322,7 +316,6 @@ The libraries prepended with a plus sign were incremented in this version.
librte_meter.so.2
librte_metrics.so.1
librte_net.so.1
- librte_pci.so.1
librte_pdump.so.2
librte_pipeline.so.3
librte_pmd_bnxt.so.2
--
2.17.2
next prev parent reply other threads:[~2018-10-15 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 14:50 [dpdk-dev] [PATCH 1/6] doc: add missing shared library versions to " Ferruh Yigit
2018-10-15 14:50 ` [dpdk-dev] [PATCH 2/6] doc: remove shared libs with no API from " Ferruh Yigit
2018-10-16 13:01 ` Jerin Jacob
2018-10-15 14:50 ` [dpdk-dev] [PATCH 3/6] doc: fix vhost library version in " Ferruh Yigit
2018-10-16 2:19 ` Tiwei Bie
2018-10-15 14:50 ` [dpdk-dev] [PATCH 4/6] mbuf: fix library version on meson build Ferruh Yigit
2018-10-15 14:25 ` Luca Boccassi
2018-10-15 14:50 ` [dpdk-dev] [PATCH 5/6] ring: add library version to " Ferruh Yigit
2018-10-15 14:26 ` Luca Boccassi
2018-10-15 14:50 ` Ferruh Yigit [this message]
2018-10-16 11:52 ` [dpdk-dev] [PATCH 6/6] doc: remove internal libs from release notes Shreyansh Jain
2018-10-25 0:07 ` Thomas Monjalon
2018-10-25 12:31 ` [dpdk-dev] [PATCH 1/6] doc: add missing shared library versions to " Thomas Monjalon
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=20181015145057.37864-6-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=yipeng1.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).