public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: phone-devel@vger.kernel.org, Rob Herring <robh@kernel.org>,
	linux-kernel@vger.kernel.org,
	Amit Pundir <amit.pundir@linaro.org>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH 1/2] config: android-recommended: Don't explicitly disable CONFIG_AIO
Date: Wed, 2 Feb 2022 10:45:59 +0100	[thread overview]
Message-ID: <YfpS19cSbsSTgKVk@kroah.com> (raw)
In-Reply-To: <20220202093314.107927-1-marijn.suijten@somainline.org>

On Wed, Feb 02, 2022 at 10:33:13AM +0100, Marijn Suijten wrote:
> Android nowadays (for a couple years already) requires AIO for at least
> its `adb` "Android Debug Bridge" [1].  Without this config option
> (`default y`) it simply refuses start, making users unable to connect to
> their phone for debugging purposes when using these kernel fragments.
> 
> [1]: https://cs.android.com/android/_/android/platform/packages/modules/adb/+/a2cb8de5e68067a5e1d002886d5f3b42d91371e1
> 
> Cc: Amit Pundir <amit.pundir@linaro.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: John Stultz <john.stultz@linaro.org>
> Signed-off-by: Marijn Suijten <marijn.suijten@somainline.org>
> ---
>  kernel/configs/android-recommended.config | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/kernel/configs/android-recommended.config b/kernel/configs/android-recommended.config
> index eb0029c9a6a6..22bd76e43aca 100644
> --- a/kernel/configs/android-recommended.config
> +++ b/kernel/configs/android-recommended.config
> @@ -1,5 +1,4 @@
>  #  KEEP ALPHABETICALLY SORTED
> -# CONFIG_AIO is not set
>  # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
>  # CONFIG_INPUT_MOUSE is not set
>  # CONFIG_LEGACY_PTYS is not set
> -- 
> 2.35.1
> 

There are lots of "required" configs now for modern Android releases, do
you want to sync up with all of them here?  If so, look at the
gki_defconfig files in the AOSP kernels for the full list of what is
required.  Is it really needed to keep this file up to date or should it
be dropped entirely given that no one has noticed how out-of-date it is?

thanks,

greg k-h

  reply	other threads:[~2022-02-02  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  9:33 [PATCH 1/2] config: android-recommended: Don't explicitly disable CONFIG_AIO Marijn Suijten
2022-02-02  9:45 ` Greg Kroah-Hartman [this message]
2022-02-02 10:12   ` Marijn Suijten
2022-02-02 10:29     ` Greg Kroah-Hartman
2022-02-02 11:28       ` Marijn Suijten

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=YfpS19cSbsSTgKVk@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.pundir@linaro.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=phone-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox