Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1736185 > unrolled thread

Android kernel configs (was Re: configs)

Started bySteve Muckle <steve.muckle@linaro.org>
First post2017-09-21 00:10 +0200
Last post2017-09-21 00:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Android kernel configs (was Re: configs) Steve Muckle <steve.muckle@linaro.org> - 2017-09-21 00:10 +0200

#1736185 — Android kernel configs (was Re: configs)

FromSteve Muckle <steve.muckle@linaro.org>
Date2017-09-21 00:10 +0200
SubjectAndroid kernel configs (was Re: configs)
Message-ID<urVlT-yv-3@gated-at.bofh.it>
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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web