From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Viktorin <viktorin@rehivetech.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 00/15] Support ARMv7 architecture
Date: Wed, 18 Nov 2015 22:45:47 +0100 [thread overview]
Message-ID: <1482016.8BKBXrqIF8@xps13> (raw)
In-Reply-To: <CALwxeUtZPMgWz_oARE9CieqRsTdZOVmupvjrLL-mDYkH1AQTsA@mail.gmail.com>
> > Jan Viktorin (7):
> > eal/arm: implement rdtsc by PMU or clock_gettime
> > eal/arm: use vector memcpy only when NEON is enabled
> > eal/arm: detect arm architecture in cpu flags
> > eal/arm: rwlock support for ARM
> > eal/arm: add very incomplete rte_vect
> > gcc/arm: avoid alignment errors to break build
> > maintainers: claim responsibility for ARMv7
> >
> > Vlastimil Kosar (8):
> > eal/arm: atomic operations for ARM
> > eal/arm: byte order operations for ARM
> > eal/arm: cpu cycle operations for ARM
> > eal/arm: prefetch operations for ARM
> > eal/arm: spinlock operations for ARM (without HTM)
> > eal/arm: vector memcpy for ARM
> > eal/arm: cpu flag checks for ARM
> > mk: Introduce ARMv7 architecture
> >
> >
> Looks good to me.
> Acked-by: David Marchand <david.marchand@6wind.com>
>
> Thanks Jan.
Applied, thanks
The rte_vect patch is squashed/removed because Jerin's patch replace it.
prev parent reply other threads:[~2015-11-18 21:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 23:47 Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 01/15] eal/arm: atomic operations for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 02/15] eal/arm: byte order " Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 03/15] eal/arm: cpu cycle " Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 04/15] eal/arm: implement rdtsc by PMU or clock_gettime Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 05/15] eal/arm: prefetch operations for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 06/15] eal/arm: spinlock operations for ARM (without HTM) Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 07/15] eal/arm: vector memcpy for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 08/15] eal/arm: use vector memcpy only when NEON is enabled Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 09/15] eal/arm: cpu flag checks for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 10/15] eal/arm: detect arm architecture in cpu flags Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 11/15] eal/arm: rwlock support for ARM Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 12/15] eal/arm: add very incomplete rte_vect Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 13/15] gcc/arm: avoid alignment errors to break build Jan Viktorin
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 14/15] mk: Introduce ARMv7 architecture Jan Viktorin
2015-11-03 10:16 ` Hunt, David
2015-11-03 10:24 ` Bruce Richardson
2015-11-03 11:18 ` Thomas Monjalon
2015-11-03 10:27 ` Jan Viktorin
2015-11-03 11:08 ` Hunt, David
2015-11-02 23:47 ` [dpdk-dev] [PATCH v6 15/15] maintainers: claim responsibility for ARMv7 Jan Viktorin
2015-11-03 4:49 ` [dpdk-dev] [PATCH v6 00/15] Support ARMv7 architecture Jerin Jacob
2015-11-03 11:33 ` Hunt, David
2015-11-03 12:32 ` Jacob, Jerin
2015-11-16 21:33 ` David Marchand
2015-11-18 21:45 ` Thomas Monjalon [this message]
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=1482016.8BKBXrqIF8@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=viktorin@rehivetech.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).