From: stillcompiling@gmail.com (Joshua Clayton)
To: linux-arm-kernel@lists.infradead.org
Subject: CONFIG_ZBOOT_ROM_TEXT and CONFIG_ZBOOT_ROM_BSS in defconfig
Date: Wed, 18 May 2016 10:38:20 -0700 [thread overview]
Message-ID: <20160518103820.0f244706@jclayton-pc> (raw)
In-Reply-To: <573C2819.3090109@free.fr>
On Wed, 18 May 2016 10:30:17 +0200
Mason <slash.tmp@free.fr> wrote:
> On 17/05/2016 17:56, Mason wrote:
>
> > I can submit a patch changing the default from 0 to 0x0, i.e.
> > no functional change. The two entries would then disappear
> > from defconfigs.
>
> Specifically, this is what I meant:
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 70764838dfcc..6831c46a3672 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1823,7 +1823,7 @@ config DEPRECATED_PARAM_STRUCT
> # TEXT and BSS so we preserve their values in the config files.
> config ZBOOT_ROM_TEXT
> hex "Compressed ROM boot loader base address"
> - default "0"
> + default 0x0
> help
> The physical address at which the ROM-able zImage is to be
> placed in the target. Platforms which normally make use of
> @@ -1834,7 +1834,7 @@ config ZBOOT_ROM_TEXT
>
> config ZBOOT_ROM_BSS
> hex "Compressed ROM boot loader BSS address"
> - default "0"
> + default 0x0
> help
> The base address of an area of read/write memory in the
> target for the ROM-able zImage which must be available while the
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
If the goal is to get rid of the 0x0's in the defconfigs, would it not
be just as effective to drop those so they land at "0"?
prev parent reply other threads:[~2016-05-18 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 15:56 CONFIG_ZBOOT_ROM_TEXT and CONFIG_ZBOOT_ROM_BSS in defconfig Mason
2016-05-18 8:30 ` Mason
2016-05-18 17:38 ` Joshua Clayton [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=20160518103820.0f244706@jclayton-pc \
--to=stillcompiling@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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