From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/t2080rdb: Add T2080PCIe-RDB board support
Date: Mon, 3 Mar 2014 08:56:40 -0800 [thread overview]
Message-ID: <5314B448.7000402@freescale.com> (raw)
In-Reply-To: <6ffc0af3cc5440db8a026a3a46117763@DM2PR03MB398.namprd03.prod.outlook.com>
On 03/03/2014 12:41 AM, Liu Shengzhou-B36685 wrote:
>> -----Original Message-----
>> From: Sun York-R58495
>> Sent: Saturday, March 01, 2014 12:48 AM
>> To: Liu Shengzhou-B36685; u-boot at lists.denx.de
>> Subject: Re: [PATCH] powerpc/t2080rdb: Add T2080PCIe-RDB board support
>>
>> On 02/28/2014 02:21 AM, Shengzhou Liu wrote:
>>>
>>>
>> Shengzhou,
>>
>> I have said with your T2081QDS patch
>>
>> "
>> Next time, please format the patch with this command
>>
>> git format-patch -M -C --find-copies-harder "
>>
>> I believe you didn't create these files from scratch. By using the proper
>> command, you will format the patch to identify copies and moves. The
>> change set will be smaller and easier to review.
>>
>> York
>
> At first, I used the patch generated by 'git format-patch -M -C --find-copies-harder', but found
> it can't directly apply to u-boot-mpc85xx base tree with conflictions, so I removed '-M -C --find-copies-harder'
> option, then it can directly apply to u-boot-mpc85xx tree without conflictions.
>
That's strange. I just did exactly the same and I can apply the patch cleanly.
York
prev parent reply other threads:[~2014-03-03 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 10:21 [U-Boot] [PATCH] powerpc/t2080rdb: Add T2080PCIe-RDB board support Shengzhou Liu
2014-02-28 16:48 ` York Sun
2014-03-03 8:41 ` Shengzhou.Liu at freescale.com
2014-03-03 16:56 ` York Sun [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=5314B448.7000402@freescale.com \
--to=yorksun@freescale.com \
--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