From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>,
kbuild test robot <lkp@intel.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] MIPS: DTS: Fix build errors used with various configs
Date: Thu, 28 May 2020 09:44:31 +0200 [thread overview]
Message-ID: <20200528074431.GA10708@alpha.franken.de> (raw)
In-Reply-To: <1590631141-23904-1-git-send-email-yangtiezhu@loongson.cn>
On Thu, May 28, 2020 at 09:59:01AM +0800, Tiezhu Yang wrote:
> If CONFIG_MIPS_MALTA is not set but CONFIG_LEGACY_BOARD_SEAD3 is set,
> the subdir arch/mips/boot/dts/mti will not be built, so the sead3.dts
> which depends on CONFIG_LEGACY_BOARD_SEAD3 in this subdir is also not
> built, and then there exists the following build error, fix it.
>
> LD .tmp_vmlinux.kallsyms1
> arch/mips/generic/board-sead3.o:(.mips.machines.init+0x4): undefined reference to `__dtb_sead3_begin'
> Makefile:1106: recipe for target 'vmlinux' failed
> make: *** [vmlinux] Error 1
>
> Additionally, add CONFIG_FIT_IMAGE_FDT_BOSTON check for subdir img to
> fix the following build error when CONFIG_MACH_PISTACHIO is not set but
> CONFIG_FIT_IMAGE_FDT_BOSTON is set.
>
> FATAL ERROR: Couldn't open "boot/dts/img/boston.dtb": No such file or directory
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Fixes: 41528ba6afe6 ("MIPS: DTS: Only build subdir of current platform")
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> arch/mips/boot/dts/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-05-28 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 1:59 [PATCH] MIPS: DTS: Fix build errors used with various configs Tiezhu Yang
2020-05-28 7:44 ` Thomas Bogendoerfer [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=20200528074431.GA10708@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lixuefeng@loongson.cn \
--cc=lkp@intel.com \
--cc=yangtiezhu@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).