From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Linux PM list <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] cpufreq: scpi-cpufreq: signedness bug in scpi_get_dvfs_info()
Date: Thu, 24 Dec 2015 09:53:52 +0000 [thread overview]
Message-ID: <567BC0B0.6070406@arm.com> (raw)
In-Reply-To: <1952184.nII0v5K5QD@vostro.rjw.lan>
On 24/12/15 01:45, Rafael J. Wysocki wrote:
> On Wednesday, December 23, 2015 11:20:04 AM Sudeep Holla wrote:
>> Hi Rafael,
>>
>> On Tue, Dec 15, 2015 at 11:16 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>> From: Dan Carpenter <dan.carpenter@oracle.com>
>>>
>>> The "domain" variable needs to be signed for the error handling to work.
>>>
>>> Fixes: 8def31034d03 ('cpufreq: arm_big_little: add SCPI interface driver')
>>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>>> Acked-by: Sudeep Holla <sudeep.holla@arm.com>
>>> ---
>>> drivers/cpufreq/scpi-cpufreq.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> Hi Rafael,
>>>
>>> This patch seem to have slipped through the cracks somehow. I don't see
>>> in patchwork too. So I am resending so that you can pick for your next
>>> rc fix if you plan to send one else for -next
>>>
>>
>> This got missed again, can you please ensure to pull this for your next -rc.
>> If you have none planned, please pull this for-next.
>
> Applied now, thanks!
>
> I'm going to push it for -rc7.
>
Thanks, sorry for the nags.
--
Regards,
Sudeep
next prev parent reply other threads:[~2015-12-24 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 11:16 [PATCH] cpufreq: scpi-cpufreq: signedness bug in scpi_get_dvfs_info() Sudeep Holla
2015-12-23 11:20 ` Sudeep Holla
2015-12-24 1:45 ` Rafael J. Wysocki
2015-12-24 9:53 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-22 19:52 [patch] " Dan Carpenter
2015-10-22 19:52 ` Dan Carpenter
2015-10-22 19:52 ` Dan Carpenter
2015-10-23 1:59 ` Viresh Kumar
2015-10-23 1:59 ` Viresh Kumar
2015-10-23 1:59 ` Viresh Kumar
2015-10-23 10:16 ` Sudeep Holla
2015-10-23 10:16 ` Sudeep Holla
2015-10-23 10:16 ` Sudeep Holla
2015-11-26 14:07 ` Sudeep Holla
2015-11-26 14:07 ` Sudeep Holla
2015-11-26 14:07 ` Sudeep Holla
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=567BC0B0.6070406@arm.com \
--to=sudeep.holla@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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 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.