From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
maxime.coquelin@st.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, ajitpal.singh@st.com
Subject: Re: [PICKME 0/2] cpufreq: New ST driver
Date: Fri, 11 Dec 2015 08:49:00 +0530 [thread overview]
Message-ID: <20151211031900.GM3612@ubuntu> (raw)
In-Reply-To: <2896628.JCDQCVfIaC@vostro.rjw.lan>
On 10-12-15, 22:38, Rafael J. Wysocki wrote:
> Do they depend on anything special?
My opp-binding-parsing patches which you applied to bleeding-edge.
Yes, Lee should have mentioned that explicitly.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PICKME 0/2] cpufreq: New ST driver
Date: Fri, 11 Dec 2015 08:49:00 +0530 [thread overview]
Message-ID: <20151211031900.GM3612@ubuntu> (raw)
In-Reply-To: <2896628.JCDQCVfIaC@vostro.rjw.lan>
On 10-12-15, 22:38, Rafael J. Wysocki wrote:
> Do they depend on anything special?
My opp-binding-parsing patches which you applied to bleeding-edge.
Yes, Lee should have mentioned that explicitly.
--
viresh
next prev parent reply other threads:[~2015-12-11 3:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 9:42 [PICKME 0/2] cpufreq: New ST driver Lee Jones
2015-12-10 9:42 ` Lee Jones
2015-12-10 9:42 ` [PICKME 1/2] cpufreq: st: Provide runtime initialised driver for ST's platforms Lee Jones
2015-12-10 9:42 ` Lee Jones
2015-12-10 9:42 ` Lee Jones
2015-12-10 9:42 ` [PICKME 2/2] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Lee Jones
2015-12-10 9:42 ` Lee Jones
2015-12-10 9:45 ` [PICKME 0/2] cpufreq: New ST driver Viresh Kumar
2015-12-10 9:45 ` Viresh Kumar
2015-12-10 21:38 ` Rafael J. Wysocki
2015-12-10 21:38 ` Rafael J. Wysocki
2015-12-11 3:19 ` Viresh Kumar [this message]
2015-12-11 3:19 ` Viresh Kumar
2015-12-11 7:05 ` Lee Jones
2015-12-11 7:05 ` Lee Jones
2015-12-15 0:01 ` Rafael J. Wysocki
2015-12-15 0:01 ` Rafael J. Wysocki
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=20151211031900.GM3612@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=ajitpal.singh@st.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=rjw@rjwysocki.net \
/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.