From: Ulf Hansson <ulf.hansson@linaro.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-tegra <linux-tegra@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] NVIDIA Tegra core power domain follow up
Date: Wed, 2 Jun 2021 09:38:01 +0200 [thread overview]
Message-ID: <CAPDyKFpMCkp5tHHcZJZf6sC4+C_xGGnhUWJg5+6hHbDT8FD_Bg@mail.gmail.com> (raw)
In-Reply-To: <20210601231003.9845-1-digetx@gmail.com>
On Wed, 2 Jun 2021 at 01:10, Dmitry Osipenko <digetx@gmail.com> wrote:
>
> Remove the lockdep_set_class(), which Ulf Hansson asked for. And
> prevent core domain syncing if domain node is missing in device-tree,
> which I accidentally missed to add after squashing the standalone
> domain driver into the PMC driver.
>
> Dmitry Osipenko (2):
> soc/tegra: pmc: Don't sync core domain if it's missing in device-tree
> soc/tegra: pmc: Remove usage of lockdep_set_class()
>
> drivers/soc/tegra/pmc.c | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
Kind regards
Uffe
next prev parent reply other threads:[~2021-06-02 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 23:10 [PATCH v1 0/2] NVIDIA Tegra core power domain follow up Dmitry Osipenko
2021-06-01 23:10 ` [PATCH v1 1/2] soc/tegra: pmc: Don't sync core domain if it's missing in device-tree Dmitry Osipenko
2021-06-01 23:10 ` [PATCH v1 2/2] soc/tegra: pmc: Remove usage of lockdep_set_class() Dmitry Osipenko
2021-06-02 7:38 ` Ulf Hansson [this message]
2021-06-02 9:10 ` [PATCH v1 0/2] NVIDIA Tegra core power domain follow up Thierry Reding
2021-06-02 10:00 ` Ulf Hansson
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=CAPDyKFpMCkp5tHHcZJZf6sC4+C_xGGnhUWJg5+6hHbDT8FD_Bg@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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.