From: Viresh Kumar <viresh.kumar@linaro.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
linux-pm@vger.kernel.org,
Antoine Tenart <antoine.tenart@bootlin.com>,
Gregory Clement <gregory.clement@bootlin.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Nadav Haklai <nadavh@marvell.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] cpufreq: add suspend/resume support in Armada 37xx DVFS driver
Date: Tue, 24 Apr 2018 11:39:22 +0530 [thread overview]
Message-ID: <20180424060922.GE2989@vireshk-i7> (raw)
In-Reply-To: <20180423163843.2b9e18b2@xps13>
On 23-04-18, 16:38, Miquel Raynal wrote:
> How would you proceed then? Shall I continue in this path? I checked
> all the drivers currently registering the cpufreq-dt driver, none of
> them use this structure, so I am open to suggestions.
I have sent you a series, please test that one.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: add suspend/resume support in Armada 37xx DVFS driver
Date: Tue, 24 Apr 2018 11:39:22 +0530 [thread overview]
Message-ID: <20180424060922.GE2989@vireshk-i7> (raw)
In-Reply-To: <20180423163843.2b9e18b2@xps13>
On 23-04-18, 16:38, Miquel Raynal wrote:
> How would you proceed then? Shall I continue in this path? I checked
> all the drivers currently registering the cpufreq-dt driver, none of
> them use this structure, so I am open to suggestions.
I have sent you a series, please test that one.
--
viresh
next prev parent reply other threads:[~2018-04-24 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 14:19 [PATCH] cpufreq: add suspend/resume support in Armada 37xx DVFS driver Miquel Raynal
2018-04-21 14:19 ` Miquel Raynal
2018-04-23 4:27 ` Viresh Kumar
2018-04-23 4:27 ` Viresh Kumar
2018-04-23 14:38 ` Miquel Raynal
2018-04-23 14:38 ` Miquel Raynal
2018-04-24 6:09 ` Viresh Kumar [this message]
2018-04-24 6:09 ` 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=20180424060922.GE2989@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=nadavh@marvell.com \
--cc=rjw@rjwysocki.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@bootlin.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 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.