linux-kernel - Android kernel configs (was Re: configs)

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

Message-ID: <d884e487-6585-5a8a-51ad-e3e36e315e08@linaro.org>
Date:   Wed, 20 Sep 2017 15:03:57 -0700
From:   Steve Muckle <steve.muckle@...aro.org>
To:     John Stultz <john.stultz@...aro.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, Greg KH <gregkh@...gle.com>,
        romlem@...gle.com
Subject: Android kernel configs (was Re: configs)

On 09/19/2017 10:08 AM, John Stultz wrote:
> So what I was thinking of to improve the developer usability might be
> the following:
> 
> 1) Leave the upstream configs in place.  We can try to keep
> maintaining them, but its not something the Android team is likely to
> care greatly about, and hopefully can be ignored. Meanwhile for the
> folks tinkering with upstream, there's something that helps them
> figure things out. When the next android-x.y tree comes out, you can
> simply remove it.
> 
> 2) To the android-x.y branches, add a script to the kernel/configs/
> dir to fetch the current config directly from the config repo. This
> way its simple for folks to get the right thing w/o looking anything
> up. This won't fly upstream, but should be fine for common.git
> 
> Thoughts?

LGTM. If anyone has concerns let me know, otherwise I'll proceed with #2.

thanks,
Steve