From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] defconfig: am43xx_hs_evm: Sync HS defconfig with non-HS defconfig
Date: Thu, 9 Feb 2017 09:27:27 -0500 [thread overview]
Message-ID: <20170209142727.GX26129@bill-the-cat> (raw)
In-Reply-To: <38bea32e-3acf-8873-6434-88b38b5e5582@ti.com>
On Thu, Feb 09, 2017 at 09:45:26AM +0530, Lokesh Vutla wrote:
>
>
> On Thursday 09 February 2017 02:02 AM, Andrew F. Davis wrote:
> > The non-HS defconfig has been modified without equivalent changes being
> > applied to the HS defconfig. Sync these here.
> >
> > Signed-off-by: Andrew F. Davis <afd@ti.com>
>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>
> I am sure we might encounter this problem again after some time :(
Well, the good news is I think we can do something about this soon now.
In the kernel we now have:
commit 237e3ad0f195d8fd34f1299e45f04793832a16fc
Author: Nicolas Pitre <nicolas.pitre@linaro.org>
Date: Fri Nov 11 00:10:05 2016 -0500
Kconfig: Introduce the "imply" keyword
And cherry-picking this, and maybe the preceding commit will let us move
lots of these logic into arch/arm/Kconfig where we can imply lots of
features that an SoC has but still allow them to be turned off.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170209/7a596273/attachment.sig>
next prev parent reply other threads:[~2017-02-09 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 20:32 [U-Boot] [PATCH] defconfig: am43xx_hs_evm: Sync HS defconfig with non-HS defconfig Andrew F. Davis
2017-02-09 4:15 ` Lokesh Vutla
2017-02-09 14:27 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-07 23:02 Andrew F. Davis
2017-04-07 13:21 ` Andrew F. Davis
2017-04-07 13:23 ` Tom Rini
2017-04-07 13:31 ` Andrew F. Davis
2017-04-07 13:48 ` Tom Rini
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=20170209142727.GX26129@bill-the-cat \
--to=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