public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: "Justin M. Forbes" <[email protected]>,
	[email protected], [email protected],
	[email protected]
Subject: Re: [PATCH] io_uring: Remove CONFIG_EXPERT
Date: Wed, 26 May 2021 23:55:41 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 5/26/21 11:34 PM, Justin M. Forbes wrote:
> While IO_URING has been in fairly heavy development, it is hidden behind
> CONFIG_EXPERT with a default of on.  It has been long enough now that I
> think we should remove EXPERT and allow users and distros to decide how
> they want this config option set without jumping through hoops.

Acked-by: Pavel Begunkov <[email protected]>


> Signed-off-by: Justin M. Forbes <[email protected]>
> ---
>  init/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/init/Kconfig b/init/Kconfig
> index 1ea12c64e4c9..0decca696bf7 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1621,7 +1621,7 @@ config AIO
>  	  this option saves about 7k.
> 
>  config IO_URING
> -	bool "Enable IO uring support" if EXPERT
> +	bool "Enable IO uring support"
>  	select IO_WQ
>  	default y
>  	help
> 

-- 
Pavel Begunkov

  reply	other threads:[~2021-05-26 22:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 22:34 [PATCH] io_uring: Remove CONFIG_EXPERT Justin M. Forbes
2021-05-26 22:55 ` Pavel Begunkov [this message]
2021-05-27 13:43 ` Jens Axboe
2021-05-27 14:12   ` Justin Forbes
2021-05-27 14:19     ` Jens Axboe
2021-05-27 16:01       ` Justin Forbes
2021-05-28  7:59         ` David Laight
2021-06-03 15:43         ` Justin Forbes
2021-06-03 15:46           ` Jens Axboe

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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