All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: Zhang Rui <rui.zhang@intel.com>, linux-pm@vger.kernel.org
Subject: Re: [PATCH] thermal: cut the spaces when user sets policy
Date: Mon, 06 May 2013 10:39:07 +0300	[thread overview]
Message-ID: <1367825947.8465.14.camel@smile> (raw)
In-Reply-To: <5183D8E7.8040708@ti.com>

On Fri, 2013-05-03 at 11:33 -0400, Eduardo Valentin wrote: 
> On 03-05-2013 09:52, Andy Shevchenko wrote:
> > Setting policy results in invalid value error.
> > 	% echo "step_wise" > policy
> > 	% echo: write error: Invalid argument
> > 
> > Need clean up of the buffer which "echo" may add based on the arguments, before
> > comparing aganist list of governor names.

> > @@ -716,7 +717,7 @@ policy_store(struct device *dev, struct device_attribute *attr,
> >  
> >  	mutex_lock(&thermal_governor_lock);
> >  
> > -	gov = __find_governor(buf);
> > +	gov = __find_governor(strim(buf));
> 
> I am much happier with this approach, much cleaner and does the job. On
> the other hand, this patch introduces a compilation warning that we want
> to avoid:
> drivers/thermal/thermal_sys.c: In function 'policy_store':
> drivers/thermal/thermal_sys.c:708: warning: passing argument 1 of
> 'strim' discards qualifiers from pointer target type
> include/linux/string.h:63: note: expected 'char *' but argument is of
> type 'const char *'
> 

Oops.
What about introduce temporary variable and pass it as a parameter?
It seems explicit casting looks not good, though it makes the job.


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

      reply	other threads:[~2013-05-06  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 13:52 [PATCH] thermal: cut the spaces when user sets policy Andy Shevchenko
2013-05-03 15:33 ` Eduardo Valentin
2013-05-06  7:39   ` 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=1367825947.8465.14.camel@smile \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=eduardo.valentin@ti.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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.