From: Andes <uboot@andestech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/3] Rename ax25-ae350 defconfig
Date: Tue, 18 Dec 2018 09:48:30 +0800 [thread overview]
Message-ID: <20181218014833.26634-1-uboot@andestech.com> (raw)
From: Rick Chen <rick@andestech.com>
Remove cpu name from the defconfig naming.
Because other cpus maybe run on AE350 platform.
So only use platfrom name in defconfig naming
will be better.
Changes since v2:
- Fix travis failure case 6.51 Checkfor configs without MAINTAINERS entry.
https://travis-ci.org/rickchen36/u-boot-riscv/builds/468881778
So add this two patchs:
MAINTAINERS: Sync for ax25-ae350 rename
doc: README.ae350: Sync for ax25-ae350 rename
Changes since v1:
- Use git mv and git format-patch -M to show delta when rename.
Rick Chen (3):
riscv: configs: Rename ax25-ae350 defconfig
MAINTAINERS: Sync for ax25-ae350 rename
doc: README.ae350: Sync for ax25-ae350 rename
board/AndesTech/ax25-ae350/MAINTAINERS | 5 ++---
configs/a25-ae350_32_defconfig | 36 ---------------------------------
configs/ae350_rv32_defconfig | 36 +++++++++++++++++++++++++++++++++
configs/ae350_rv64_defconfig | 37 ++++++++++++++++++++++++++++++++++
configs/ax25-ae350_64_defconfig | 37 ----------------------------------
doc/README.ae350 | 2 +-
6 files changed, 76 insertions(+), 77 deletions(-)
delete mode 100644 configs/a25-ae350_32_defconfig
create mode 100644 configs/ae350_rv32_defconfig
create mode 100644 configs/ae350_rv64_defconfig
delete mode 100644 configs/ax25-ae350_64_defconfig
--
2.7.4
next reply other threads:[~2018-12-18 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 1:48 Andes [this message]
2018-12-18 1:48 ` [U-Boot] [PATCH v3 1/3] riscv: configs: Rename ax25-ae350 defconfig Andes
2018-12-18 1:48 ` [U-Boot] [PATCH v3 2/3] MAINTAINERS: Sync for ax25-ae350 rename Andes
2018-12-18 2:12 ` Bin Meng
2018-12-18 2:23 ` Rick Chen
2018-12-18 2:49 ` Bin Meng
2018-12-18 2:54 ` Rick Chen
2018-12-18 1:48 ` [U-Boot] [PATCH v3 3/3] doc: README.ae350: " Andes
2018-12-18 2:13 ` Bin Meng
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=20181218014833.26634-1-uboot@andestech.com \
--to=uboot@andestech.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