From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH defconfig] ARM: add ARM_SINGLE_ARMV7M in ARMv7-M defconfigs
Date: Thu, 21 May 2015 11:27:48 +0200 [thread overview]
Message-ID: <2ddf1a3a6386cf4bb692b7a202346910@agner.ch> (raw)
In-Reply-To: <20150521082604.GZ24769@pengutronix.de>
On 2015-05-21 10:26, Uwe Kleine-K?nig wrote:
> On Thu, May 21, 2015 at 12:38:21AM +0200, Stefan Agner wrote:
>> Select ARM_SINGLE_ARMV7M in defconfigs of the converted ARMv7-M
>> platforms.
> I assume this relates to your series that introduces this symbol. Should
> the defconfig update happen before? (Or what is the result if
> CONFIG_ARM_SINGLE_ARMV7M=y is missing in the defconfig while the symbol
> already exists?) Maybe this should be squashed into the commit in
> question?
The Kconfig system defaults to versatile then, it tried yesterday and I
think it and it compiled fine actually. However, it is of course not
what the user wants.
The defconfigs of the new machines are currently in arm-soc
next/defconfig. While testing, I just merged the defconfig branch into
the soc branch, but then splitted the patch in two independent patches.
Arnd, what do you think?
--
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Agner <stefan@agner.ch>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>, arnd@arndb.de
Cc: linux@arm.linux.org.uk, manabian@gmail.com,
linux-kernel@vger.kernel.org, mcoquelin.stm32@gmail.com,
olof@lixom.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH defconfig] ARM: add ARM_SINGLE_ARMV7M in ARMv7-M defconfigs
Date: Thu, 21 May 2015 11:27:48 +0200 [thread overview]
Message-ID: <2ddf1a3a6386cf4bb692b7a202346910@agner.ch> (raw)
In-Reply-To: <20150521082604.GZ24769@pengutronix.de>
On 2015-05-21 10:26, Uwe Kleine-König wrote:
> On Thu, May 21, 2015 at 12:38:21AM +0200, Stefan Agner wrote:
>> Select ARM_SINGLE_ARMV7M in defconfigs of the converted ARMv7-M
>> platforms.
> I assume this relates to your series that introduces this symbol. Should
> the defconfig update happen before? (Or what is the result if
> CONFIG_ARM_SINGLE_ARMV7M=y is missing in the defconfig while the symbol
> already exists?) Maybe this should be squashed into the commit in
> question?
The Kconfig system defaults to versatile then, it tried yesterday and I
think it and it compiled fine actually. However, it is of course not
what the user wants.
The defconfigs of the new machines are currently in arm-soc
next/defconfig. While testing, I just merged the defconfig branch into
the soc branch, but then splitted the patch in two independent patches.
Arnd, what do you think?
--
Stefan
next prev parent reply other threads:[~2015-05-21 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 22:38 [PATCH defconfig] ARM: add ARM_SINGLE_ARMV7M in ARMv7-M defconfigs Stefan Agner
2015-05-20 22:38 ` Stefan Agner
2015-05-21 8:26 ` Uwe Kleine-König
2015-05-21 8:26 ` Uwe Kleine-König
2015-05-21 9:27 ` Stefan Agner [this message]
2015-05-21 9:27 ` Stefan Agner
2015-05-22 14:56 ` Arnd Bergmann
2015-05-22 14:56 ` Arnd Bergmann
2015-05-21 17:01 ` Joachim Eastwood
2015-05-21 17:01 ` Joachim Eastwood
2015-05-22 14:59 ` Arnd Bergmann
2015-05-22 14:59 ` Arnd Bergmann
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=2ddf1a3a6386cf4bb692b7a202346910@agner.ch \
--to=stefan@agner.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.