From: Leo Liang <ycliang@andestech.com>
To: Zong Li <zong.li@sifive.com>
Cc: <u-boot@lists.denx.de>
Subject: Re: [PATCH] board: sifive: drop stuff related to unmatched revision 1
Date: Wed, 14 Jul 2021 14:55:54 +0800 [thread overview]
Message-ID: <20210714065554.GA3237@andestech.com> (raw)
In-Reply-To: <20210709080601.20397-1-zong.li@sifive.com>
Hi Zong,
On Fri, Jul 09, 2021 at 04:06:01PM +0800, Zong Li wrote:
> This patch reverts the following commits:
> - 4b4159d0f3 ("riscv: dts: add dts for unmatched rev1")
> - ffe9a394df ("board: sifive: support spl multi-dtb on unmatched board")
>
> We won't plan to support unmatched that the revision below 3 in u-boot,
> so they can be dropped because they might be useless.
>
> Signed-off-by: Zong Li <zong.li@sifive.com>
> Suggested-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
> ---
> arch/riscv/dts/Makefile | 2 +-
> .../fu740-hifive-unmatched-a00-ddr-rev1.dtsi | 1489 -----------------
> .../dts/hifive-unmatched-a00-rev1-u-boot.dtsi | 7 -
> arch/riscv/dts/hifive-unmatched-a00-rev1.dts | 4 -
> board/sifive/unmatched/spl.c | 28 +-
> configs/sifive_unmatched_defconfig | 4 -
I found that the order of the CONFIGs in "sifive_unmatched_defconfig"
has been rearranged by this commit "fd075f77ca configs: Resync with savedefconfig",
so this patch does not apply anymore.
Could you please rebase on u-boot/master and then send the patch again? Thanks!
Best regards,
Leo
> 6 files changed, 3 insertions(+), 1531 deletions(-)
> delete mode 100644 arch/riscv/dts/fu740-hifive-unmatched-a00-ddr-rev1.dtsi
> delete mode 100644 arch/riscv/dts/hifive-unmatched-a00-rev1-u-boot.dtsi
> delete mode 100644 arch/riscv/dts/hifive-unmatched-a00-rev1.dts
next prev parent reply other threads:[~2021-07-14 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 8:06 [PATCH] board: sifive: drop stuff related to unmatched revision 1 Zong Li
2021-07-12 13:22 ` Leo Liang
2021-07-14 6:55 ` Leo Liang [this message]
2021-07-20 6:28 ` Zong Li
2021-07-14 11:22 ` Bin Meng
2021-07-14 11:31 ` David Abdurachmanov
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=20210714065554.GA3237@andestech.com \
--to=ycliang@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=zong.li@sifive.com \
/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