All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Leo Liang <ycliang@andestech.com>, Green Wan <green.wan@sifive.com>
Cc: rick@andestech.com, u-boot@lists.denx.de
Subject: Re: [PULL] u-boot-riscv/master
Date: Wed, 26 May 2021 11:24:35 -0400	[thread overview]
Message-ID: <20210526152435.GF17669@bill-the-cat> (raw)
In-Reply-To: <20210526081249.GA19414@andestech.com>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

On Wed, May 26, 2021 at 04:12:50PM +0800, Leo Liang wrote:

> Hi Tom,
> 
> The following changes since commit eb53b943be2949ca111140a8e05532cd74cda058:
> 
>   Merge https://source.denx.de/u-boot/custodians/u-boot-sh (2021-05-23 10:15:15 -0400)
> 
> are available in the Git repository at:
> 
>   git@source.denx.de:u-boot/custodians/u-boot-riscv.git 
> 
> for you to fetch changes up to 9358576a281ab5e3b7348685bbd5f713833a5048:
> 
>   drivers: pci: pcie_dw_common: fix Werror compilation error (2021-05-24 23:54:54 +0800)
> 
> Gitlab CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/7620
> 

NAK.
ERROR: fdt or initrd relocation disabled at boot time
#993: FILE: include/configs/sifive-unmatched.h:65:
+       "fdt_high=0xffffffffffffffff\0" \

ERROR: fdt or initrd relocation disabled at boot time
#994: FILE: include/configs/sifive-unmatched.h:66:
+       "initrd_high=0xffffffffffffffff\0" \

You can, but shouldn't disable initrd relocation.  You cannot disable
device tree relocation as that leads to too many issues due to
misalignment later.  Make use of bootm_size or similar to make sure
everything is within an appropriate area of memory.  Thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2021-05-26 15:24 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  8:12 [PULL] u-boot-riscv/master Leo Liang
2021-05-26 15:24 ` Tom Rini [this message]
2021-05-27  8:57   ` Green Wan
2021-05-27 10:41     ` Leo Liang
2021-05-27 11:20       ` Tom Rini
2021-05-27 13:56         ` Green Wan
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 11:41 Leo Liang
2023-10-19 14:57 ` Tom Rini
2023-10-05  8:10 Leo Liang
2023-10-05 17:46 ` Tom Rini
2023-09-26  5:21 Leo Liang
2023-09-26 14:05 ` Tom Rini
2023-09-21  1:36 Leo Liang
2023-09-21 19:57 ` Tom Rini
2023-09-05  3:30 Leo Liang
2023-09-05 18:43 ` Tom Rini
2023-08-10 10:32 Leo Liang
2023-08-10 16:22 ` Tom Rini
2023-08-02  5:48 Leo Liang
2023-08-02  6:27 ` Bin Meng
2023-08-02  9:31   ` Leo Liang
2023-08-03  0:59     ` Minda Chen
2023-07-24  8:01 Leo Liang
2023-07-24 16:41 ` Tom Rini
2023-07-12  6:58 Leo Liang
2023-07-12 19:43 ` Tom Rini
2023-04-21  0:41 Leo Liang
2023-04-23 16:15 ` Tom Rini
2023-02-17 12:12 Leo Liang
2023-02-17 15:01 ` Tom Rini
2023-02-19  6:09   ` Leo Liang
2023-02-02  6:30 Leo Liang
2023-02-02 19:18 ` Tom Rini
2022-12-08 11:23 Leo Liang
2022-12-08 16:24 ` Tom Rini
2022-11-16  6:16 Leo Liang
2022-11-16 18:01 ` Tom Rini
2022-11-03  7:04 Leo Liang
2022-11-03 16:57 ` Tom Rini
2022-11-04  0:28   ` Leo Liang
2022-10-20 12:36 Leo Liang
2022-10-20 19:03 ` Tom Rini
2022-09-06  6:07 Leo Liang
2022-09-06 15:50 ` Tom Rini
2022-08-11 21:38 Leo Liang
2022-08-12 12:17 ` Tom Rini
2022-05-27  2:36 Leo Liang
2022-05-27 13:30 ` Tom Rini
2022-05-28  9:02   ` Leo Liang
2022-05-30 15:05     ` Tom Rini
2022-08-11 22:22       ` Leo Liang
2022-04-06  4:43 Leo Liang
2022-04-06 15:55 ` Tom Rini
2022-03-16  2:56 Leo Liang
2022-03-16 14:48 ` Tom Rini
2022-02-10 15:16 Leo Liang
2022-02-11  0:35 ` Tom Rini
2021-12-03  6:19 Leo Liang
2021-12-04 17:50 ` Tom Rini
2021-11-09  2:40 Leo Liang
2021-11-09 13:45 ` Tom Rini
2021-10-20  7:14 Leo Liang
2021-10-21 11:51 ` Tom Rini
2021-10-07 11:51 Leo Liang
2021-10-07 15:43 ` Tom Rini
2021-09-07  8:20 Leo Liang
2021-09-07 15:33 ` Tom Rini
2021-08-19  8:56 Leo Liang
2021-08-19 14:13 ` Tom Rini
2021-07-22  2:15 Leo Liang
2021-07-22 12:15 ` Tom Rini
2021-07-07 15:21 Leo Liang
2021-07-07 17:33 ` Tom Rini
2021-07-06 16:02 Leo Liang
2021-07-06 19:52 ` Tom Rini
2021-07-07  4:05   ` Tianrui Wei
2021-06-17  3:31 Leo Liang
2021-06-17 14:51 ` Tom Rini
2021-05-31 10:16 Leo Liang
2021-05-31 18:59 ` Tom Rini
2021-05-20  2:19 Leo Liang
2021-05-21 14:07 ` Tom Rini
2021-05-18  1:48 Leo Liang
2021-05-18 18:17 ` Tom Rini
2021-05-14 11:10 Leo Liang
2021-05-14 12:23 ` Bin Meng
2021-05-15 12:09 ` Tom Rini
2021-05-07  1:06 Leo Liang
2021-05-07  1:09 ` Tom Rini
2021-05-07  1:41   ` Leo Liang
2021-05-07  1:55     ` Sean Anderson
2021-05-07 16:15       ` Tom Rini
2021-05-07 14:21     ` Dimitri John Ledkov
2021-05-07 14:35       ` Tom Rini
2021-05-07  1:49 ` Sean Anderson
2021-05-10  6:57   ` Leo Liang
2021-05-07 15:37 ` Tom Rini
2021-04-08 10:44 Leo Liang
2021-04-08 19:36 ` Tom Rini

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=20210526152435.GF17669@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=green.wan@sifive.com \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.