From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linaro-acpi@lists.linaro.org, patches@linaro.org,
jaswinder.singh@linaro.org, sudeep.holla@arm.com
Subject: Re: [PATCH v5 0/6] CPUFreq driver using CPPC methods
Date: Tue, 26 May 2015 07:42:33 +0530 [thread overview]
Message-ID: <20150526021233.GE23464@linux> (raw)
In-Reply-To: <1432590581-8925-1-git-send-email-ashwin.chaugule@linaro.org>
On 25-05-15, 17:49, Ashwin Chaugule wrote:
Generate patches using --thread=shallow option of git, so that we see
all patches in a thread.
--
viresh
next prev parent reply other threads:[~2015-05-26 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 21:49 [PATCH v5 0/6] CPUFreq driver using CPPC methods Ashwin Chaugule
2015-05-26 2:12 ` Viresh Kumar [this message]
2015-05-26 11:29 ` Ashwin Chaugule
2015-05-26 11:56 ` Viresh Kumar
2015-05-26 17:23 ` [Linaro-acpi] " Al Stone
2015-05-26 18:32 ` Ashwin Chaugule
2015-05-26 20:21 ` Al Stone
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=20150526021233.GE23464@linux \
--to=viresh.kumar@linaro.org \
--cc=ashwin.chaugule@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.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 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).