From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Paul Walmsley <pwalmsley@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
Allen Martin <amartin@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH] soc: tegra: pmc: restrict compilation of suspend-related support to ARM
Date: Thu, 08 Jan 2015 14:23:40 +0300 [thread overview]
Message-ID: <54AE68BC.305@gmail.com> (raw)
In-Reply-To: <20150108105818.GJ1987@ulmo.nvidia.com>
08.01.2015 13:58, Thierry Reding пишет:
> On Thu, Jan 08, 2015 at 12:42:47PM +0300, Dmitry Osipenko wrote:
>> 08.01.2015 11:49, Thierry Reding пишет:
>>> I don't like changing this back to syscore_ops since it makes things
>>> less easier to follow. I also don't think that using PMC_SCRATCH41 for
>>> two different purposes is a good thing. There are a couple of
>>> suggestions in my reply to your original patch. Could you investigate
>>> whether any of those can be used to fix this instead?
>>>
>>> Thierry
>>>
>>
>> I haven't received your reply. Double checked gmail inbox and mailing lists -
>> nothing. It may just not propagated yet if you sent it today, otherwise can you
>> please re-send it?
>
> For some reason it hadn't gone out. Should be now, though.
>
> Thierry
>
Received now, thanks! Your proposal sounds interesting, I'll try it.
--
Dmitry
prev parent reply other threads:[~2015-01-08 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 22:36 [PATCH] soc: tegra: pmc: restrict compilation of suspend-related support to ARM Paul Walmsley
2014-12-10 11:23 ` Thierry Reding
2014-12-12 3:04 ` Paul Walmsley
2015-01-07 14:33 ` Thierry Reding
2015-01-07 15:24 ` Dmitry Osipenko
2015-01-07 15:55 ` Dmitry Osipenko
2015-01-08 8:49 ` Thierry Reding
2015-01-08 9:42 ` Dmitry Osipenko
2015-01-08 10:58 ` Thierry Reding
2015-01-08 11:23 ` Dmitry Osipenko [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=54AE68BC.305@gmail.com \
--to=digetx@gmail.com \
--cc=amartin@nvidia.com \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=pwalmsley@nvidia.com \
--cc=swarren@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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).