From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/t2080rdb: Add T2080PCIe-RDB board support
Date: Fri, 28 Feb 2014 08:48:23 -0800 [thread overview]
Message-ID: <5310BDD7.9050906@freescale.com> (raw)
In-Reply-To: <1393582899-30387-1-git-send-email-Shengzhou.Liu@freescale.com>
On 02/28/2014 02:21 AM, Shengzhou Liu wrote:
> ---
> board/freescale/t208xrdb/Makefile | 13 +
> board/freescale/t208xrdb/README | 196 ++++++++
> board/freescale/t208xrdb/cpld.c | 71 +++
> board/freescale/t208xrdb/cpld.h | 42 ++
> board/freescale/t208xrdb/ddr.c | 112 +++++
> board/freescale/t208xrdb/ddr.h | 47 ++
> board/freescale/t208xrdb/eth_t208xrdb.c | 106 +++++
> board/freescale/t208xrdb/law.c | 34 ++
> board/freescale/t208xrdb/pci.c | 23 +
> board/freescale/t208xrdb/t2080_pbi.cfg | 41 ++
> board/freescale/t208xrdb/t2080_rcw.cfg | 8 +
> board/freescale/t208xrdb/t208xrdb.c | 115 +++++
> board/freescale/t208xrdb/t208xrdb.h | 13 +
> board/freescale/t208xrdb/tlb.c | 151 +++++++
> boards.cfg | 5 +
> include/configs/T208xRDB.h | 779 ++++++++++++++++++++++++++++++++
> 16 files changed, 1756 insertions(+)
> create mode 100644 board/freescale/t208xrdb/Makefile
> create mode 100644 board/freescale/t208xrdb/README
> create mode 100644 board/freescale/t208xrdb/cpld.c
> create mode 100644 board/freescale/t208xrdb/cpld.h
> create mode 100644 board/freescale/t208xrdb/ddr.c
> create mode 100644 board/freescale/t208xrdb/ddr.h
> create mode 100644 board/freescale/t208xrdb/eth_t208xrdb.c
> create mode 100644 board/freescale/t208xrdb/law.c
> create mode 100644 board/freescale/t208xrdb/pci.c
> create mode 100644 board/freescale/t208xrdb/t2080_pbi.cfg
> create mode 100644 board/freescale/t208xrdb/t2080_rcw.cfg
> create mode 100644 board/freescale/t208xrdb/t208xrdb.c
> create mode 100644 board/freescale/t208xrdb/t208xrdb.h
> create mode 100644 board/freescale/t208xrdb/tlb.c
> create mode 100644 include/configs/T208xRDB.h
>
>
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
next prev parent reply other threads:[~2014-02-28 16:48 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 [this message]
2014-03-03 8:41 ` Shengzhou.Liu at freescale.com
2014-03-03 16:56 ` York Sun
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=5310BDD7.9050906@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