From: Johannes Berg <johannes@sipsolutions.net>
To: Jonas Gorski <jogo@openwrt.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luciano Coelho <luca@coelho.fi>, Kalle Valo <kvalo@adurom.com>,
dri-devel@lists.freedesktop.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v2] device coredump: add new device coredump class
Date: Fri, 05 Sep 2014 11:56:25 +0200 [thread overview]
Message-ID: <1409910985.1940.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAOiHx=nGHGEHSLABnR9NL9ZEXYJN_TvJnyGud8mxseL2089fwg@mail.gmail.com>
On Fri, 2014-09-05 at 11:40 +0200, Jonas Gorski wrote:
> On Fri, Sep 5, 2014 at 10:50 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
>
> Can't you just send from the correct address? ;p
Not easily :)
> How about the following to avoid negative options:
>
> config DEV_COREDUMP
> bool "Enable device coredump" if EXPERT
> default y if WANT_DEV_COREDUMP
> help
> Enable the device coredump mechanism for drivers wanting to
> use it. Disabling 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.
>
> If unsure, say Y.
Yeah, that seems reasonable. I guess I did the negative option because I
was thinking about the negative case ("I really don't want this!!!
111!!") :)
johannes
next prev parent reply other threads:[~2014-09-05 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 8:50 [RFC v2] device coredump: add new device coredump class Johannes Berg
2014-09-05 9:40 ` Jonas Gorski
2014-09-05 9:56 ` Johannes Berg [this message]
2014-09-05 22:13 ` Greg Kroah-Hartman
2014-09-07 9:37 ` Johannes Berg
2014-09-08 8:38 ` Johannes Berg
2014-09-12 16:40 ` Greg Kroah-Hartman
2014-09-07 7:42 ` Arik Nemtsov
2014-09-08 8:36 ` Arend van Spriel
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=1409910985.1940.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emmanuel.grumbach@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jogo@openwrt.org \
--cc=kvalo@adurom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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;
as well as URLs for NNTP newsgroup(s).