All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: allow deactivating the IEEE1394 menuconfig section at once
Date: Thu, 7 Sep 2023 19:16:01 +0900	[thread overview]
Message-ID: <20230907101601.GA33589@workstation.local> (raw)
In-Reply-To: <20230906081216.22849-1-jengelh@inai.de>

Hi,

On Wed, Sep 06, 2023 at 10:12:16AM +0200, Jan Engelhardt wrote:
> Presently, one needs to enter "FireWire (IEEE 1394) subsystem --->",
> then deselect all options individually. Speed up that process by
> making the "--->" line be togglable in its own right.
> 
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>
> ---
>  drivers/firewire/Kconfig | 14 ++++++++++++--
>  1 file changed, 12 insertions(+), 2 deletions(-)

We are at the second half of merge window for v6.6 kernel, while the patch
looks good to me. I applied it to for-next branch and will send it to Linus
within a few days, after it passes check by for-next integration.

> diff --git a/drivers/firewire/Kconfig b/drivers/firewire/Kconfig
> index 0a6596b027db..be1a9e685782 100644
> --- a/drivers/firewire/Kconfig
> +++ b/drivers/firewire/Kconfig
> @@ -1,8 +1,18 @@
>  # SPDX-License-Identifier: GPL-2.0-only
> -menu "IEEE 1394 (FireWire) support"
> +menuconfig FIREWIRE_SUPPORT
> +	bool "IEEE 1394 (FireWire) support"
> +	default y
>  	depends on PCI || COMPILE_TEST
>  	# firewire-core does not depend on PCI but is
>  	# not useful without PCI controller driver
> +	help
> +	  Support for FireWire.
> +
> +	  The answer to this question will not directly affect the
> +	  kernel: saying N will just cause the configurator to skip all
> +	  the questions about FireWire.
> +
> +if FIREWIRE_SUPPORT
>  
>  config FIREWIRE
>  	tristate "FireWire driver stack"
> @@ -96,4 +106,4 @@ config FIREWIRE_NOSY
>  
>  	  If unsure, say N.
>  
> -endmenu
> +endif # FIREWIRE_SUPPORT
> -- 
> 2.42.0


Thanks

Takashi Sakamoto

      reply	other threads:[~2023-09-07 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  8:12 [PATCH] firewire: allow deactivating the IEEE1394 menuconfig section at once Jan Engelhardt
2023-09-07 10:16 ` Takashi Sakamoto [this message]

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=20230907101601.GA33589@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=jengelh@inai.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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.