From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
patches@linaro.org
Subject: Re: [PATCH 0/5] Cpufreq Fixes for 3.9
Date: Sat, 12 Jan 2013 19:12:05 +0530 [thread overview]
Message-ID: <CAKohpon1uv1cXKJaOKQdw2_jLcOTABk86BYEicsHJjJ7Y1od_Q@mail.gmail.com> (raw)
In-Reply-To: <3417394.mgXgKYU9J9@vostro.rjw.lan>
On 12 January 2013 18:57, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> There's no need to add a Tested-by for yourself if you sign-off a patch,
> though. Tested-by is information that somebody *in* *addition* to the
> original author has tested the patch, because we all should test the patches
> we sign-off, right?
Correct. I did it this time only, as it was something major.
prev parent reply other threads:[~2013-01-12 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 5:14 [PATCH 0/5] Cpufreq Fixes for 3.9 Viresh Kumar
2013-01-12 5:14 ` [PATCH 1/5] cpufreq: Manage only online cpus Viresh Kumar
[not found] ` <cover.1357967566.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-01-12 5:14 ` [PATCH 2/5] cpufreq: Notify governors when cpus are hot-[un]plugged Viresh Kumar
2013-01-12 5:14 ` [PATCH 4/5] cpufreq: Simplify __cpufreq_remove_dev() Viresh Kumar
2013-01-12 5:14 ` [PATCH 5/5] cpufreq: Simplify cpufreq_add_dev() Viresh Kumar
2013-01-12 5:14 ` [PATCH 3/5] cpufreq: Don't use cpu removed during cpufreq_driver_unregister Viresh Kumar
2013-01-12 13:27 ` [PATCH 0/5] Cpufreq Fixes for 3.9 Rafael J. Wysocki
2013-01-12 13:42 ` Viresh Kumar [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=CAKohpon1uv1cXKJaOKQdw2_jLcOTABk86BYEicsHJjJ7Y1od_Q@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).