linux-kernel - Re: Defconfig update for LPC32xx

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] [day] [month] [year] [list]

Date:	Fri, 20 Apr 2012 14:54:08 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Roland Stigge <stigge@...com.de>
Cc:	arm@...nel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: Defconfig update for LPC32xx

On Thursday 19 April 2012, Roland Stigge wrote:
> Hi,
> 
> I'm planning to update arch/arm/configs/lpc32xx_defconfig, adjusting to
> device tree and new driver options.
> 
> Now I wonder if I should (1) just add drivers which are used on the
> reference machine (PHYTEC LPC3250 board) or (2) additionally add all
> drivers that I have seen together with LPC32xx on other boards also,
> which would demonstrate that the same binary kernel runs on all LPC32xx
> machines, but increasing kernel size a bit.
> 
> I would prefer option (2) but first want to ask for advice.

I think either way is fine, this is one of the things I would completely
leave to you as the platform maintainer.

If you know that other machines are working with the same defconfig,
it would be helpful to also have their .dts files in the kernel source
for reference, but not mandatory.

	Arnd
--
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/