All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Aristeu Rozanski <aris@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] tiny: reverse logic for DISABLE_DEV_COREDUMP
Date: Thu, 16 Oct 2014 15:44:30 +0200	[thread overview]
Message-ID: <20141016134430.GB7664@thin> (raw)
In-Reply-To: <20141016133658.GP5930@redhat.com>

On Thu, Oct 16, 2014 at 09:36:58AM -0400, Aristeu Rozanski wrote:
> (This time Cc'ing Johannes)

This kind of note shouldn't be in the commit-message portion of the
commit.

> It's desirable for allnconfig and tinyconfig targets to result in the
> least amount of code possible. DISABLE_DEV_COREDUMP exists as a way to
> switch off DEV_COREDUMP regardless if any drivers select
> WANT_DEV_COREDUMP.
> 
> This patch renames the option to ENABLE_DEV_COREDUMP and setting it to
> 'n' (as in allnconfig or tinyconfig) will effectively disable device
> coredump.
> 
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Josh Triplett <josh@joshtriplett.org>
> Cc: Johannes Berg <johannes@sipsolutions.net>
> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
> Signed-off-by: Aristeu Rozanski <arozansk@redhat.com>

You should have a "---" line here, followed by a diffstat.  If you're
not using git format-patch to format your patches, you should.

- Josh Triplett

> diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
> index 134f763..99d3072 100644
> --- a/drivers/base/Kconfig
> +++ b/drivers/base/Kconfig
> @@ -171,20 +171,23 @@ config WANT_DEV_COREDUMP
>  	  Drivers should "select" this option if they desire to use the
>  	  device coredump mechanism.
>  
> -config DISABLE_DEV_COREDUMP
> -	bool "Disable device coredump" if EXPERT
> +config ENABLE_DEV_COREDUMP
> +	bool "Enable device coredump" if EXPERT
> +	default y
>  	help
> -	  Disable the device coredump mechanism despite drivers wanting to
> -	  use it; this allows for more sensitive systems or systems that
> -	  don't want to ever access the information to not have the code,
> -	  nor keep any data.
> +	  This option controls if the device coredump mechanism is available or
> +	  not; if disabled, the mechanism will be omitted even if drivers that
> +	  can use it are enabled.
> +	  Say 'N' for more sensitive systems or systems that don't want
> +	  to ever access the information to not have the code, nor keep any
> +	  data.
>  
> -	  If unsure, say N.
> +	  If unsure, say Y.
>  
>  config DEV_COREDUMP
>  	bool
>  	default y if WANT_DEV_COREDUMP
> -	depends on !DISABLE_DEV_COREDUMP
> +	depends on ENABLE_DEV_COREDUMP
>  
>  config DEBUG_DRIVER
>  	bool "Driver Core verbose debug messages"

  reply	other threads:[~2014-10-16 13:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 13:36 [PATCH] tiny: reverse logic for DISABLE_DEV_COREDUMP Aristeu Rozanski
2014-10-16 13:44 ` Josh Triplett [this message]
2014-10-16 15:49   ` Aristeu Rozanski
2014-10-20  9:42     ` Johannes Berg
2014-10-20 11:55       ` Josh Triplett
2014-10-20 22:18         ` Greg Kroah-Hartman
2014-10-20 23:45           ` josh
2014-10-30  8:01           ` Johannes Berg
2014-10-30  9:00             ` [PATCH 3.18] tiny: rename ENABLE_DEV_COREDUMP to ALLOW_DEV_COREDUMP Johannes Berg
2014-10-30 12:55               ` Aristeu Rozanski
2014-10-30 13:32               ` Josh Triplett
  -- strict thread matches above, loose matches on Subject: below --
2014-10-15 15:25 [PATCH] tiny: reverse logic for DISABLE_DEV_COREDUMP Aristeu Rozanski
2014-10-15 23:14 ` Greg Kroah-Hartman
2014-10-16  3:51   ` Josh Triplett
2014-10-16 10:18     ` Greg Kroah-Hartman
2014-10-16 10:24       ` Josh Triplett
2014-10-16 13:02         ` Aristeu Rozanski

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=20141016134430.GB7664@thin \
    --to=josh@joshtriplett.org \
    --cc=aris@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.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.