linux-kernel - Re: [PATCH defconfig] ARM: add ARM_SINGLE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2ddf1a3a6386cf4bb692b7a202346910@agner.ch>
Date:	Thu, 21 May 2015 11:27:48 +0200
From:	Stefan Agner <stefan@...er.ch>
To:	Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
	arnd@...db.de
Cc:	linux@....linux.org.uk, manabian@...il.com,
	linux-kernel@...r.kernel.org, mcoquelin.stm32@...il.com,
	olof@...om.net, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH defconfig] ARM: add ARM_SINGLE_ARMV7M in ARMv7-M defconfigs

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/