All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Rob Herring <robh@kernel.org>,
	Amit Pundir <amit.pundir@linaro.org>,
	kernel-team@android.com
Subject: Re: [RFC][PATCH] kernel/configs: Drop Android config fragments
Date: Wed, 12 Apr 2023 08:15:15 +0200	[thread overview]
Message-ID: <2023041257-flatterer-dean-19a4@gregkh> (raw)
In-Reply-To: <20230411180409.1706067-1-jstultz@google.com>

On Tue, Apr 11, 2023 at 06:04:09PM +0000, John Stultz wrote:
> In the old days where each device had a custom kernel, the
> android config fragments were useful to provide the required
> and reccomended options expected by userland.
> 
> However, these days devices are expected to use the GKI kernel,
> so these config fragments no longer needed, and out of date, so
> they seem to only cause confusion.
> 
> So lets drop them. If folks are curious what configs are
> expected by the Android environment, check out the gki_defconfig
> file in the latest android common kernel tree.
> 
> Cc: Rob Herring <robh@kernel.org>
> Cc: Amit Pundir <amit.pundir@linaro.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: kernel-team@android.com
> Signed-off-by: John Stultz <jstultz@google.com>
> ---
>  MAINTAINERS                               |   5 -
>  kernel/configs/android-base.config        | 159 ----------------------
>  kernel/configs/android-recommended.config | 127 -----------------
>  3 files changed, 291 deletions(-)
>  delete mode 100644 kernel/configs/android-base.config
>  delete mode 100644 kernel/configs/android-recommended.config

Yeah!

I'll be glad to take this if I can get some acks.

thanks for doing this.

greg k-h

  reply	other threads:[~2023-04-12  6:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 18:04 [RFC][PATCH] kernel/configs: Drop Android config fragments John Stultz
2023-04-12  6:15 ` Greg Kroah-Hartman [this message]
2023-04-12 18:49 ` Amit Pundir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2023041257-flatterer-dean-19a4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.pundir@linaro.org \
    --cc=jstultz@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.