DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH v3 11/14] updated release note for armv8 support for DPDK 2.2
Date: Fri, 6 Nov 2015 15:10:30 +0530	[thread overview]
Message-ID: <1446802833-22265-12-git-send-email-jerin.jacob@caviumnetworks.com> (raw)
In-Reply-To: <1446802833-22265-1-git-send-email-jerin.jacob@caviumnetworks.com>

Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
 doc/guides/rel_notes/release_2_2.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst
index 43a3a3c..a3587a2 100644
--- a/doc/guides/rel_notes/release_2_2.rst
+++ b/doc/guides/rel_notes/release_2_2.rst
@@ -23,10 +23,11 @@ New Features
 
 * **Added vhost-user multiple queue support.**
 
-* **Introduce ARMv7 architecture**
+* **Introduce ARMv7 and ARMv8 architectures**
 
-  It is now possible to build DPDK for the ARMv7 platform and test with
-  virtual PMD drivers.
+  * It is now possible to build DPDK for the ARMv7 and ARMv8 platforms.
+  * ARMv7 can be tested with virtual PMD drivers.
+  * ARMv8 can be tested with virtual and physical PMD drivers.
 
 
 Resolved Issues
-- 
1.9.3

  parent reply	other threads:[~2015-11-06  9:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  9:40 [dpdk-dev] [PATCH v3 00/14] DPDK armv8-a support Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 01/14] eal: arm64: add armv8-a version of rte_atomic_64.h Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 02/14] eal: arm64: add armv8-a version of rte_cpuflags_64.h Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 03/14] eal: arm64: add armv8-a version of rte_prefetch_64.h Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 04/14] eal: arm64: add armv8-a version of rte_cycles_64.h Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 05/14] eal: arm64: rte_memcpy_64.h version based on libc memcpy Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 06/14] eal: arm: ret_vector.h improvements Jerin Jacob
2015-11-18 18:56   ` Thomas Monjalon
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 07/14] app: test_cpuflags: test the new cpu flags added for arm64 Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 08/14] acl: arm64: acl implementation using NEON gcc intrinsic Jerin Jacob
2015-11-06  9:52   ` Ananyev, Konstantin
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 09/14] mk: add support for armv8 on top of armv7 Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 10/14] mk: add support for thunderx machine target based on armv8-a Jerin Jacob
2015-11-06  9:40 ` Jerin Jacob [this message]
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 12/14] maintainers: claim responsibility for ARMv8 Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 13/14] eal: introduce rte_smp_*mb() for memory barriers to use between lcores Jerin Jacob
2015-11-06  9:40 ` [dpdk-dev] [PATCH v3 14/14] eal: arm: define rte_smp_mb(), rte_smp_wmb(), rte_smp_rmb() for arm Jerin Jacob
2015-11-18 21:48 ` [dpdk-dev] [PATCH v3 00/14] DPDK armv8-a support 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=1446802833-22265-12-git-send-email-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.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 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).