From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 1/2] doc: fix indentation of new feature in release notes
Date: Fri, 22 Jul 2016 17:06:20 +0100 [thread overview]
Message-ID: <1469203581-15234-1-git-send-email-bruce.richardson@intel.com> (raw)
The description of the new feature for external caches on mempools was
indented too much, putting it out of alignment with the other items in the
new features list in the pdf output. Correct this by removing the extra
spaces.
Fixes: 4b5062755aa7 ("mempool: allow user-owned cache")
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
doc/guides/rel_notes/release_16_07.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/guides/rel_notes/release_16_07.rst b/doc/guides/rel_notes/release_16_07.rst
index 0740d4f..1606522 100644
--- a/doc/guides/rel_notes/release_16_07.rst
+++ b/doc/guides/rel_notes/release_16_07.rst
@@ -40,9 +40,9 @@ New Features
* **Added mempool external cache for non-EAL thread.**
- Added new functions to create, free or flush a user-owned mempool
- cache for non-EAL threads. Previously, cache was always disabled
- on these threads.
+ Added new functions to create, free or flush a user-owned mempool
+ cache for non-EAL threads. Previously, cache was always disabled
+ on these threads.
* **Changed the memory allocation in mempool library.**
--
2.7.4
next reply other threads:[~2016-07-22 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 16:06 Bruce Richardson [this message]
2016-07-22 16:06 ` [dpdk-dev] [PATCH 2/2] doc: improve wording of new features section Bruce Richardson
2016-07-22 16:19 ` Thomas Monjalon
2016-07-25 8:39 ` Bruce Richardson
2016-07-27 13:26 ` [dpdk-dev] [PATCH v2] " John McNamara
2016-07-28 15:25 ` 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=1469203581-15234-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).