From: Andre Przywara <andre.przywara@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/5] ARM: vexpress: create A9 specific board config
Date: Thu, 04 Apr 2013 12:31:08 +0200 [thread overview]
Message-ID: <515D566C.1040301@linaro.org> (raw)
In-Reply-To: <20130404120954.18d9e04a@lilith>
On 04/04/2013 12:09 PM, Albert ARIBAUD wrote:
> Hi Andre,
>
> On Wed, 3 Apr 2013 15:44:33 +0200, Andre Przywara
> <andre.przywara@linaro.org> wrote:
>
>> From: Ryan Harkin <ryan.harkin@linaro.org>
>>
>> This patch creates a new config for the A9 quad core tile that includes the
>> generic config for the Versatile Express platform.
>>
>> Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
>> Signed-off-by: Andre Przywara <andre.przywara@linaro.org>
>> ---
>> MAINTAINERS | 2 +-
>> boards.cfg | 2 +-
>> include/configs/vexpress_ca9x4.h | 34 ++++++++++++++++++++++++++++++++++
>> include/configs/vexpress_common.h | 1 -
>> 4 files changed, 36 insertions(+), 3 deletions(-)
>> create mode 100644 include/configs/vexpress_ca9x4.h
>
> Wait, so patch 1/5 renames ca9x4_ct_vxp as vexpress_common, then patch
> 2/5 renames vexpress_common as vexpress_ca9x4? If so then please make
> this a single patch without the intermediary/temporary step.
But that would not mark the actual file copy (vexpress_common.h is
almost the same as vexpress_ca9x4.h) as such, right?
So you would end up with a completely new file (_common.h) and
a file with almost all content deleted (_ca9x4.h). The fact that the
code just moved wouldn't be obvious.
That would be extra pity with the nice -M move features in the previous
patch.
However I have no problems with merging these two, if you insist.
Regards,
Andre.
next prev parent reply other threads:[~2013-04-04 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 13:44 [U-Boot] [PATCH 0/5] ARM: vexpress: add support for more core tiles Andre Przywara
2013-04-03 13:44 ` [U-Boot] [PATCH 1/5] ARM: vexpress: move files in preparation for adding a new platform Andre Przywara
2013-04-04 10:06 ` Albert ARIBAUD
2013-04-04 10:30 ` Andre Przywara
2013-04-03 13:44 ` [U-Boot] [PATCH 2/5] ARM: vexpress: create A9 specific board config Andre Przywara
2013-04-04 10:09 ` Albert ARIBAUD
2013-04-04 10:31 ` Andre Przywara [this message]
2013-04-04 11:13 ` Albert ARIBAUD
2013-04-03 13:44 ` [U-Boot] [PATCH 3/5] ARM: vexpress: create A5 " Andre Przywara
2013-04-03 13:44 ` [U-Boot] [PATCH 4/5] ARM: vexpress: add support for Versatile Express Cortex-A15-TC2 Andre Przywara
2013-04-03 13:44 ` [U-Boot] [PATCH 5/5] ARM: vexpress: enable bootz and hush parser for all VExpress boards Andre Przywara
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=515D566C.1040301@linaro.org \
--to=andre.przywara@linaro.org \
--cc=u-boot@lists.denx.de \
/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