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]
Message-ID: <20161213080816.dafyhoqhodytyy3j@pengutronix.de>
Date:   Tue, 13 Dec 2016 09:08:16 +0100
From:   Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>
To:     Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Cc:     linux-arm-kernel@...ts.infradead.org,
        Olof Johansson <olof@...om.net>,
        Russell King <linux@....linux.org.uk>,
        linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>
Subject: Re: [RFC PATCH 00/23] arm: defconfigs: use kconfig fragments

Hallo,

On Tue, Dec 06, 2016 at 01:38:35PM +0100, Bartlomiej Zolnierkiewicz wrote:
> This RFC patchset starts convertion of ARM defconfigs to use kconfig
> fragments and dynamically generate defconfigs.  The goals of this
> work are to:
> 
> - remove duplication between defconfigs
> 
> - add a possibility to generate board/SoC/SoC-family/Multi specific
>   defconfigs in the future (without duplicating defconfigs)

what is the main use case for defconfigs? If it's the start point for
users to get a working configuration for their machine, the idea might
be fine. If however todays most important use case is build coverage,
it's even a disadvantage to make the different configs more uniform.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ