mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dan Williams <djbw@fb.com>
Cc: 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>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: [PATCH 1/3] dmatest: make module parameters writable
Date: Thu, 08 Aug 2013 11:42:06 +0300	[thread overview]
Message-ID: <1375951326.403.25.camel@smile> (raw)
In-Reply-To: <CE2134A4.1D1FD%djbw@fb.com>

On Fri, 2013-08-02 at 17:49 +0000, Dan Williams wrote: 
> 
> On 7/31/13 7:28 AM, "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
> wrote:
> 
> >On Tue, 2013-07-23 at 18:36 +0300, Andy Shevchenko wrote:
> >> The debugfs interface brought a copy of the test case parameters. This
> >>makes
> >> different set of values under /sys/module/dmatest/parameters/ and
> >> /sys/kernel/debug/dmatest/. The user might be confused by the
> >>divergence of
> >> values.
> >> 
> >> The proposed solution in this patch is to make module parameters
> >>writable and
> >> remove them from the debugfs. Though we're still using debugfs to
> >>control test
> >> runner and getting results.
> >> 
> >> Documentation part is updated accordingly.
> >> 
> >> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >> Suggested-by: Dan Williams <djbw@fb.com>
> >
> >Dan, do you have any comments against this series?
> >I'd like to have this incorporated into v3.12.
> 
> I like this direction, and these can go in as is.  

So, could it be considered as your ACK?
If so, I think it would be better to push it early to be in time for
v3.12

> But I think with a bit
> more work we can eventually trim the Œresults' file and the
> thread_{add|get}_result infrastructure.  Ideally we could move all result
> reporting to ftrace and let a module parameter control which errors are
> reported.
> 
> However, unless I missed it, I don¹t see this support[1] upstream yet.
> 
> 
> --
> Dan
> 
> [1]: https://lwn.net/Articles/432186/
> 

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      parent reply	other threads:[~2013-08-08  8:42 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
2013-08-08  8:42     ` Andy Shevchenko [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=1375951326.403.25.camel@smile \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=djbw@fb.com \
    --cc=jerome.blin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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