From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7: add HREFv60 to multi_v7 defconfig
Date: Mon, 16 Sep 2013 08:15:50 -0500 [thread overview]
Message-ID: <CAL_Jsq+GDfez+a3EdrEUdZVfj8c8An89NWOW3RCUjvZPf-PrOQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqK=mZJkhyS0pVtvqZSFjO6262xwZuh5Y_VTfuuJk73FuA@mail.gmail.com>
On Mon, Sep 16, 2013 at 8:11 AM, Rob Herring <robherring2@gmail.com> wrote:
> On Mon, Sep 16, 2013 at 7:22 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> This is just a standard board for the Ux500, include it in the
>> v7 multiplatform defconfig.
>>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>> ---
>> Hi ARM SoC folks: this makes also my preferred development board
>> boot with multi_v7. Please apply this patch directly to fixes
>> if you're happy with it.
>> ---
>> arch/arm/configs/multi_v7_defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
>> index 6e572c6..a333753 100644
>> --- a/arch/arm/configs/multi_v7_defconfig
>> +++ b/arch/arm/configs/multi_v7_defconfig
>> @@ -36,6 +36,7 @@ CONFIG_ARCH_TEGRA_114_SOC=y
>> CONFIG_TEGRA_PCI=y
>> CONFIG_TEGRA_EMC_SCALING_ENABLE=y
>> CONFIG_ARCH_U8500=y
>> +CONFIG_MACH_HREFV60=y
>
> This option doesn't seem to actually affect the build in anyway. Same
> with snowball. Why not remove them?
Well, I've already forgotten how mach-types works... So the only
difference is a machine desc included or not. Why not just always
include all machines.
Rob
next prev parent reply other threads:[~2013-09-16 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 12:22 [PATCH] ARM: multi_v7: add HREFv60 to multi_v7 defconfig Linus Walleij
2013-09-16 13:11 ` Rob Herring
2013-09-16 13:15 ` Rob Herring [this message]
2013-09-16 14:41 ` Russell King - ARM Linux
2013-09-16 14:54 ` Olof Johansson
2013-09-17 9:16 ` Linus Walleij
2013-09-18 19:15 ` Olof Johansson
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=CAL_Jsq+GDfez+a3EdrEUdZVfj8c8An89NWOW3RCUjvZPf-PrOQ@mail.gmail.com \
--to=robherring2@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;
as well as URLs for NNTP newsgroup(s).