From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH v2 2/2] Migrate bootlimit to Kconfig
Date: Wed, 18 Jul 2018 23:08:44 +0200 [thread overview]
Message-ID: <20180718230844.0450c440@jawa> (raw)
In-Reply-To: <20180714075944.6943-3-alex.kiernan@gmail.com>
Hi Alex,
> Migrate boards which set bootlimit in the environment to Kconfig.
>
> We exclude gurnard_defconfig which includes a bootlimit=, but doesn't
> set CONFIG_BOOTCOUNT_LIMIT, so we'd fail to include a bootlimit
> setting if we migrated it.
>
> display5_defconfig and display5_factory_defconfig share a
> SYS_CONFIG_NAME, but only display5_defconfig enables
> CONFIG_BOOTCOUNT_LIMIT, so we fail to set bootlimit= in
> display5_factory_defconfig. This is okay because the
> display5_factory_defconfig doesn't need to have it set, as it is only
> meant to prepare the board in the factory.
>
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> ---
>
> Changes in v2:
> - include display5 in the migration to Kconfig
Reviewed-by: Lukasz Majewski <lukma@denx.de>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180718/ea776b0b/attachment.sig>
prev parent reply other threads:[~2018-07-18 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 7:59 [U-Boot] [RESEND PATCH v2 0/2] Add bootlimit to Kconfig Alex Kiernan
2018-07-14 7:59 ` [U-Boot] [RESEND PATCH v2 1/2] Add BOOTCOUNT_BOOTLIMIT to set reboot limit Alex Kiernan
2018-07-15 9:36 ` Prabhakar Kushwaha
2018-07-15 15:47 ` Alex Kiernan
2018-07-14 7:59 ` [U-Boot] [RESEND PATCH v2 2/2] Migrate bootlimit to Kconfig Alex Kiernan
2018-07-18 21:08 ` Lukasz Majewski [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=20180718230844.0450c440@jawa \
--to=lukma@denx.de \
--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