public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Marcin Wojtas <mw@semihalf.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Leif Lindholm" <leif.lindholm@linaro.org>,
	"Nadav Haklai" <nadavh@marvell.com>,
	"Neta Zur Hershkovits" <neta@marvell.com>,
	"Kostya Porotchkin" <kostap@marvell.com>,
	"Hua Jing" <jinghua@marvell.com>, "Jan Dąbroś" <jsd@semihalf.com>
Subject: Re: [platforms: PATCH 0/5] Armada 7k/8k files reorganization
Date: Thu, 7 Dec 2017 20:11:16 +0100	[thread overview]
Message-ID: <CAPv3WKeF-4X8PH7QKQAQQ-s0EbB5sp1dZcZ8vCaZDujXX7+ncw@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu-RD4A8uEPoWV6ZM5wfieZ6HXC2m1nr116u1_7qBwVvAA@mail.gmail.com>

2017-12-07 20:07 GMT+01:00 Ard Biesheuvel <ard.biesheuvel@linaro.org>:
> On 7 December 2017 at 19:06, Marcin Wojtas <mw@semihalf.com> wrote:
>> Hi Ard,
>>
>> 2017-12-07 17:48 GMT+01:00 Ard Biesheuvel <ard.biesheuvel@linaro.org>:
>>> On 7 December 2017 at 16:31, Marcin Wojtas <mw@semihalf.com> wrote:
>>>> Hi,
>>>>
>>>> I submit a long awaited file reorganization of Marvell Armada 7k/8k
>>>> SoC family support. Armada 70x0 DB files remained in
>>>> 'Platform/Marvell', SoC files, drivers, libraries, etc. were
>>>> shifted to 'Silicon/Marvell'.
>>>>
>>>> Although there are no functional changes, other most significant
>>>> modifications are:
>>>> - use 'Armada7k8k' name/prefix, reflecting the SoC family properly
>>>> - use 'Armada70x0Db' for a board files
>>>> - move and rename the SPI master driver
>>>> - move and rename the PciEmulation driver
>>>> - rename output fd file for Armada70x0Db
>>>>
>>>> More details can be found in the commit log. In order to get a
>>>> better overview, please check 'tree' command outputs below.
>>>>
>>>> The code is available in the github:
>>>> https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/reorg-upstream-r20171207
>>>>
>>>> I'm looking forward to your feedback.
>>>>
>>>
>>> Hi Marcin,
>>>
>>> Could you regenerate these patches with rename detection please?
>>>
>>
>> For every single operation I used 'git mv'. 'git status' showed the
>> renaming properly and so does 'git show -M' on my branch. I'll search
>> for better 'git format-patch' generation, but if you know  the trick,
>> please share.
>>
>
> git format-patch -M does not work for you?

'git format-patch --find-renames' works fine. I'll issue v2 right away.

Thanks,
Marcin


      reply	other threads:[~2017-12-07 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 16:31 [platforms: PATCH 0/5] Armada 7k/8k files reorganization Marcin Wojtas
2017-12-07 16:31 ` [platforms: PATCH 1/5] Marvell: Reorganize file structure Marcin Wojtas
2017-12-07 16:31 ` [platforms: PATCH 2/5] Marvell/Armada7k8k: Use '7k8k' prefix in the SoC drivers/libraries Marcin Wojtas
2017-12-07 16:31 ` [platforms: PATCH 3/5] Marvell/Armada70x0Db: Rename fd file Marcin Wojtas
2017-12-07 16:31 ` [platforms: PATCH 4/5] Marvell/Drivers: Rename SPI master driver Marcin Wojtas
2017-12-07 16:31 ` [platforms: PATCH 5/5] Marvell/Drivers: Drop 'PciEmulation' naming Marcin Wojtas
2017-12-07 16:48 ` [platforms: PATCH 0/5] Armada 7k/8k files reorganization Ard Biesheuvel
2017-12-07 19:06   ` Marcin Wojtas
2017-12-07 19:07     ` Ard Biesheuvel
2017-12-07 19:11       ` Marcin Wojtas [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-list 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=CAPv3WKeF-4X8PH7QKQAQQ-s0EbB5sp1dZcZ8vCaZDujXX7+ncw@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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