mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Jon Medhurst <tixy@linaro.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] cpufreq: make return type of lock_policy_rwsem_{read|write}() as void
Date: Wed, 02 Oct 2013 18:38:04 +0200	[thread overview]
Message-ID: <1472934.KdmdpVCX1h@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomoqp0dtS+TG-Johsh=o6VefeqByD0bM_DLXg+qYhQ5+g@mail.gmail.com>

On Wednesday, October 02, 2013 02:13:36 PM Viresh Kumar wrote:
> On 30 September 2013 23:58, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Monday, September 16, 2013 08:40:17 PM Viresh Kumar wrote:
> >> lock_policy_rwsem_{read|write}() currently has return type of int but it always
> >> return zero and hence its return type must be void instead. This patch makes its
> >> return type void and fixes all users of it as well.
> >>
> >> Reported-by: Jon Medhurst<tixy@linaro.org>
> >> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> >
> > This doesn't apply to bleeding-edge for me any more after I have applied your
> > series of 44 patches to it.  Care to resend?
> 
> Done..

Which one is it?


  reply	other threads:[~2013-10-02 16:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 15:10 [PATCH 1/2] cpufreq: unlock correct rwsem while updating policy->cpu Viresh Kumar
2013-09-16 15:10 ` [PATCH 2/2] cpufreq: make return type of lock_policy_rwsem_{read|write}() as void Viresh Kumar
2013-09-17  8:28   ` Jon Medhurst (Tixy)
2013-09-30 18:28   ` Rafael J. Wysocki
2013-10-02  8:43     ` Viresh Kumar
2013-10-02 16:38       ` Rafael J. Wysocki [this message]
2013-10-02 16:49         ` Viresh Kumar
2013-09-16 16:27 ` [PATCH 1/2] cpufreq: unlock correct rwsem while updating policy->cpu Jon Medhurst (Tixy)
2013-09-16 17:08   ` Viresh Kumar
2013-09-16 18:34     ` Rafael J. Wysocki
2013-09-17  4:38       ` Viresh Kumar
2013-09-16 18:42     ` Jon Medhurst (Tixy)
2013-09-17  4:46       ` Viresh Kumar

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=1472934.KdmdpVCX1h@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=tixy@linaro.org \
    --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

all inboxes | Powered by JetHome®