From: Andre Przywara <andre.przywara@arm.com>
To: Tom Rini <trini@konsulko.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Simon Glass <sjg@chromium.org>,
Samuel Holland <samuel@sholland.org>,
linux-sunxi@lists.linux.dev,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/2] sunxi: Kconfig: use SoC-wide values for some symbols
Date: Wed, 14 Sep 2022 15:24:00 +0100 [thread overview]
Message-ID: <20220914152400.1e9fe273@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <20220914140444.GQ6993@bill-the-cat>
On Wed, 14 Sep 2022 10:04:44 -0400
Tom Rini <trini@konsulko.com> wrote:
Hi Tom,
> On Wed, Sep 14, 2022 at 12:32:16AM +0100, Andre Przywara wrote:
>
> > Some configuration symbols formerly defined in header files were
> > recently converted to Kconfig symbols. This moved their value definition
> > into *every* defconfig file, even though those values are hardly board
> > choices.
> > Use the new Kconfig option to define per-SoC default values, in just one
> > place, which makes the definition in each defconfig file redundant.
> >
> > We refrain from setting a sunxi specific value for CONFIG_SYS_BOOTM_LEN,
> > so this defaults to a much better 64MB for uncompressed arm64 kernels.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@arm.com>
>
> Note that you forgot to CC the U-Boot list on this series.
>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Many thanks! And yeah, I realised that missing CC: afterwards, and sent it
again, just to the list this time. CC:ing now to record your tag.
Cheers,
Andre
next prev parent reply other threads:[~2022-09-14 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 23:32 [PATCH 0/2] sunxi: defconfig: use Kconfig defaults Andre Przywara
2022-09-13 23:32 ` [PATCH 1/2] sunxi: Kconfig: use SoC-wide values for some symbols Andre Przywara
2022-09-14 14:04 ` Tom Rini
2022-09-14 14:24 ` Andre Przywara [this message]
2022-09-13 23:32 ` [PATCH 2/2] sunxi: defconfig: drop redundant definitions Andre Przywara
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=20220914152400.1e9fe273@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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;
as well as URLs for NNTP newsgroup(s).