From: Jesse Taube <mr.bossman075@gmail.com>
To: Tnze Jdao <cjd001113@outlook.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: "giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>
Subject: Re: [PATCH 00/11] Add support for SUNIV and F1C100s.
Date: Sat, 15 Jan 2022 16:02:05 -0500 [thread overview]
Message-ID: <9ea3dfed-515e-4e60-189f-4e965a2d8e6e@gmail.com> (raw)
In-Reply-To: <OSZPR01MB69239EE7AB71E24B1909B681B3509@OSZPR01MB6923.jpnprd01.prod.outlook.com>
On 1/10/22 00:13, Tnze Jdao wrote:
> I tested this patch and tried to run it on my LicheePi Nano. It works, but I found there is WARNINGs when compile the code:
> -------
> include/configs/sunxi-common.h:128:0: warning: "CONFIG_ENV_SECT_SIZE" redefined
> #define CONFIG_ENV_SECT_SIZE 0x1000
Ah I will move this it should be moved to defconfig thx for pointing
this out.
>
> In file included from ././include/linux/kconfig.h:4:0,
> from <command-line>:0:
> include/generated/autoconf.h:296:0: note: this is the location of the previous definition
> #define CONFIG_ENV_SECT_SIZE 0x1
Not entirely sure how it got defined here, it doesn't get defined in my
generated config.
>
> In file included from include/configs/suniv.h:12:0,
> from include/config.h:4,
> from include/common.h:16,
> from lib/slre.c:24:
> --------
> And I think the problem is the CONFIG_ENV_SECT_SIZE should be (and required to) defined in the config file rather than at include/configs/sunxi-common.h:128
Im sorry for the late reply the email got lost.
next prev parent reply other threads:[~2022-01-15 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 5:13 [PATCH 00/11] Add support for SUNIV and F1C100s Tnze Jdao
2022-01-15 21:02 ` Jesse Taube [this message]
2022-01-20 18:12 ` Chris Morgan
2022-01-20 18:34 ` Jesse Taube
-- strict thread matches above, loose matches on Subject: below --
2022-01-05 0:34 Jesse Taube
2022-01-05 11:36 ` Icenowy Zheng
2022-01-05 12:14 ` Andre Przywara
2022-01-05 12:54 ` Jesse Taube
2022-01-05 16:00 ` Giulio Benetti
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=9ea3dfed-515e-4e60-189f-4e965a2d8e6e@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=cjd001113@outlook.com \
--cc=giulio.benetti@benettiengineering.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 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.