linux-kernel - Proposal: single defconfig for all ARM

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

Message-ID: <CAOuPNLj80zQYzUju9hmvKPU1jytEnMHidEQ=Ph8L8cTVnHuK=g@mail.gmail.com>
Date:   Thu, 26 Oct 2017 21:56:13 +0530
From:   Pintu Kumar <pintu.ping@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Proposal: single defconfig for all ARM

Hi,

My proposal is to maintain a common base defconfig file for all ARM
products and only add the additional configs in the new defconfig
file.
I am not sure if this is already possible. If this is possible please
let us know the steps.

For example:
Under arch/arm/configs , there are more than 100 defconfig files.
Now, in many of these defconfig files there could be many similar
CONFIG that my be enabled. Thus many repeated entries.
If we create new defconfig file we end up copying again the repeated entries.

Instead can we do something like this:
1) Maintain common ARM specific CONFIG into: arm_base_defconfig
2) Then in chipset specific defconfig: <chipset>_defconfig
     Maintain only new entries.
     At the top just include the base config like this:
     include arm_base_defconfig

Thus we can avoid repeated entries.
Or can we use something like the VARIANT_DEFCONFIG

Please let us know your suggestions.

Thanks,
Pintu