Re: [PATCH 1/3] dmatest: make module parameters writable

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: Dan Williams <djbw@fb.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	"Blin, Jerome" <jerome.blin@intel.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 1/3] dmatest: make module parameters writable
Date: Fri, 2 Aug 2013 18:03:29 +0000	[thread overview]
Message-ID: <CE2141DE.1D2FE%djbw@fb.com> (raw)
In-Reply-To: <1375466216.22073.6.camel@gandalf.local.home>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="euc-kr", Size: 989 bytes --]



On 8/2/13 10:56 AM, "Steven Rostedt" <rostedt@goodmis.org> wrote:

>On Fri, 2013-08-02 at 17:49 +0000, Dan Williams wrote:
>
>> However, unless I missed it, I don©öt see this support[1] upstream yet.
>> 
>> 
>> --
>> Dan
>> 
>> [1]: https://lwn.net/Articles/432186/
>
>IIRC, there was some push back from doing this. I don't really remember
>who? Rusty maybe?
>
>Or maybe not, it seems he had some comments on it in that thread:
>
>http://thread.gmane.org/gmane.linux.kernel/1110481
>
>Perhaps I got busy and dropped it :-/
>
>Anyway, if there's a demand for it, we can always revisit the idea.

Dmatest has infrastructure to collect a list of test result messages and
output them on-demand when reading a debugfs file.  I figure we might as
well trace them but would want to enable the tracepoints when the module
is loaded.

ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éÝ¶\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dÊ‡Ú™ë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

next prev parent reply	other threads:[~2013-08-02 18:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 15:36 Andy Shevchenko
2013-07-23 15:36 ` [PATCH 2/3] dmatest: remove IS_ERR_OR_NULL checks of debugfs calls Andy Shevchenko
2013-07-23 15:36 ` [PATCH 3/3] dmatest: print message on debug level in case of no error Andy Shevchenko
2013-07-31 14:28 ` [PATCH 1/3] dmatest: make module parameters writable Andy Shevchenko
2013-08-02 17:49   ` Dan Williams
2013-08-02 17:56     ` Steven Rostedt
2013-08-02 18:03       ` Dan Williams [this message]
2013-08-08  8:42     ` Andy Shevchenko

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=CE2141DE.1D2FE%djbw@fb.com \
    --to=djbw@fb.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=jerome.blin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome