From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Vlastimil Kosar <kosar@rehivetech.com>, dev@dpdk.org
Subject: Re: [PATCH v6 14/15] mk: Introduce ARMv7 architecture
Date: Tue, 03 Nov 2015 12:18:21 +0100 [thread overview]
Message-ID: <1494965.qdxxxY3pyY@xps13> (raw)
In-Reply-To: <20151103102435.GD15320@bricha3-MOBL3>
2015-11-03 10:24, Bruce Richardson:
> The release notes "New Feature" section is always one that causes conflicts on
> apply of patches. I think Thomas is ok to handle that on apply, or else we'd all
> be constantly rebasing.
Yes, it is a common conflict managed when applying.
> For 2.3 we maybe need to come up with a new way to modify this to make applying
> patches easier. For example, can the new features section just be pulled from
> a set of individual single-bullet-point files inside a directory? Then each new
> feature just drops its addition in a new file and there are no conflicts. Can
> rst be used to pull into a doc a directory: e.g. "new_features/*.rst"?
Good idea.
But we should try to have some automatic sorting in the list.
next prev parent reply other threads:[~2015-11-03 11:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 23:47 [PATCH v6 00/15] Support ARMv7 architecture Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 01/15] eal/arm: atomic operations for ARM Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 02/15] eal/arm: byte order " Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 03/15] eal/arm: cpu cycle " Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 04/15] eal/arm: implement rdtsc by PMU or clock_gettime Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 05/15] eal/arm: prefetch operations for ARM Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 06/15] eal/arm: spinlock operations for ARM (without HTM) Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 07/15] eal/arm: vector memcpy for ARM Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 08/15] eal/arm: use vector memcpy only when NEON is enabled Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 09/15] eal/arm: cpu flag checks for ARM Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 10/15] eal/arm: detect arm architecture in cpu flags Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 11/15] eal/arm: rwlock support for ARM Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 12/15] eal/arm: add very incomplete rte_vect Jan Viktorin
2015-11-02 23:47 ` [PATCH v6 13/15] gcc/arm: avoid alignment errors to break build Jan Viktorin
2015-11-02 23:47 ` [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 [this message]
2015-11-03 10:27 ` Jan Viktorin
2015-11-03 11:08 ` Hunt, David
2015-11-02 23:47 ` [PATCH v6 15/15] maintainers: claim responsibility for ARMv7 Jan Viktorin
2015-11-03 4:49 ` [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
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=1494965.qdxxxY3pyY@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kosar@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 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.