Subject: Android kernel configs (was Re: configs)
To: John Stultz <john.stultz@linaro.org>
References: <CAHWC2xKxZ6jFex0Zq2EKW-Opo-n5sHVvyZmFfLMe93mVpBa-hg@mail.gmail.com>
 <CALAqxLUwnfF+DENhUME2BgXBtz=1XbODayEbUrbkEJKJ=xh_GQ@mail.gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <gregkh@google.com>,
        romlem@google.com
From: Steve Muckle <steve.muckle@linaro.org>
Message-ID: <d884e487-6585-5a8a-51ad-e3e36e315e08@linaro.org>
Date: Wed, 20 Sep 2017 15:03:57 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CALAqxLUwnfF+DENhUME2BgXBtz=1XbODayEbUrbkEJKJ=xh_GQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 881
Lines: 22

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