From: Stephen Boyd <sboyd@kernel.org>
To: Sowjanya Komatineni <skomatineni@nvidia.com>,
jonathanh@nvidia.com, mturquette@baylibre.com,
pgaikwad@nvidia.com, thierry.reding@gmail.com
Cc: digetx@gmail.com, pdeschrijver@nvidia.com,
linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: tegra: clk-dfll: Fix to remove pm_runtime_irq_safe
Date: Tue, 12 Nov 2019 14:46:46 -0800 [thread overview]
Message-ID: <20191112224647.39F572084E@mail.kernel.org> (raw)
In-Reply-To: <1573575426-31314-1-git-send-email-skomatineni@nvidia.com>
Quoting Sowjanya Komatineni (2019-11-12 08:17:05)
> This patch includes fix to remove pm_runtime_irq_safe which was added
> mistakenly during dfll suspend and resume implementation as a part of
> Tegra210 SC7 suspend and resume patch series.
>
> This patch removes pm_runtime_irq_safe and also has minor description
> update for argument of dfll_suspend in comments.
>
> Some of the patch series are applied so sending this fix as incremental
> fix to latest linux-next.
Please don't send cover letters for single patches. The value add is
minimal vs. just putting extra text next to the diffstat in the single
patch.
>
> Sowjanya Komatineni (1):
> clk: tegra: clk-dfll: Fix to remove pm_runtime_irq_safe
>
> drivers/clk/tegra/clk-dfll.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
prev parent reply other threads:[~2019-11-12 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 16:17 [PATCH v1] clk: tegra: clk-dfll: Fix to remove pm_runtime_irq_safe Sowjanya Komatineni
2019-11-12 16:17 ` Sowjanya Komatineni
2019-11-12 16:17 ` Sowjanya Komatineni
2019-11-12 16:17 ` Sowjanya Komatineni
2019-11-13 16:22 ` Dmitry Osipenko
2019-11-12 22:46 ` Stephen Boyd [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=20191112224647.39F572084E@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=skomatineni@nvidia.com \
--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.