From: Dan Williams <dan.j.williams@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] [nomination] Move Fast and Oops Things
Date: Wed, 21 May 2014 21:04:27 -0700 [thread overview]
Message-ID: <CAPcyv4i3Kki80QRzEszGNC__-NLY_K_QdbMNp0BFzDkSkoc-_w@mail.gmail.com> (raw)
In-Reply-To: <20140522094835.3bf5ba5a@notabene.brown>
On Wed, May 21, 2014 at 4:48 PM, NeilBrown <neilb@suse.de> wrote:
[..]
> What might the control interface look like
> I imagine something like dynamic_debug, which a file that lists all the
> dynamic_config options. Writing some message to the file would enable the
> selected options, and so the dynamic code editing required to enable it.
Ooh, yes, an interface similar to dynamic debug control seems like a good fit.
> I think it is probably worth trying - see what sort of take-up it gets.
Thanks Neil! ...as everyone else moans, "don't encourage him". ;-)
next prev parent reply other threads:[~2014-05-22 4:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 23:13 Dan Williams
2014-05-16 2:56 ` NeilBrown
2014-05-16 15:04 ` Chris Mason
2014-05-16 17:09 ` Andy Grover
2014-05-23 8:11 ` Dan Carpenter
2014-05-16 18:31 ` Randy Dunlap
2014-05-21 7:48 ` Dan Williams
2014-05-21 7:55 ` Greg KH
2014-05-21 9:05 ` Matt Fleming
2014-05-21 12:52 ` Greg KH
2014-05-21 13:23 ` Matt Fleming
2014-05-21 8:25 ` NeilBrown
2014-05-21 8:36 ` Dan Williams
2014-05-21 8:53 ` Matt Fleming
2014-05-21 10:11 ` NeilBrown
2014-05-21 15:35 ` Dan Williams
2014-05-21 23:06 ` Rafael J. Wysocki
2014-05-21 23:03 ` Dan Williams
2014-05-21 23:40 ` Laurent Pinchart
2014-05-22 0:10 ` Rafael J. Wysocki
2014-05-22 15:48 ` Theodore Ts'o
2014-05-22 16:31 ` Dan Williams
2014-05-22 17:38 ` Theodore Ts'o
2014-05-22 18:42 ` Dan Williams
2014-05-22 19:06 ` Chris Mason
2014-05-22 20:31 ` Dan Carpenter
2014-05-22 20:56 ` Geert Uytterhoeven
2014-05-23 6:21 ` James Bottomley
2014-05-23 14:11 ` John W. Linville
2014-05-24 9:14 ` James Bottomley
2014-05-24 19:19 ` Geert Uytterhoeven
2014-05-23 2:13 ` Greg KH
2014-05-23 3:03 ` Dan Williams
2014-05-23 7:44 ` Greg KH
2014-05-23 14:02 ` Josh Boyer
2014-05-21 23:48 ` NeilBrown
2014-05-22 4:04 ` Dan Williams [this message]
2014-05-21 7:22 ` Dan Williams
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=CAPcyv4i3Kki80QRzEszGNC__-NLY_K_QdbMNp0BFzDkSkoc-_w@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=neilb@suse.de \
/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