From: Mark Brown <broonie@kernel.org>
To: kjlu@umn.edu, Dinghao Liu <dinghao.liu@zju.edu.cn>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
linux-spi@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-tegra@vger.kernel.org,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] spi: tegra20-slink: Fix runtime PM imbalance on error
Date: Thu, 28 May 2020 14:07:55 +0100 [thread overview]
Message-ID: <159067126729.55053.1525159932135385920.b4-ty@kernel.org> (raw)
In-Reply-To: <20200523122909.25247-1-dinghao.liu@zju.edu.cn>
On Sat, 23 May 2020 20:29:09 +0800, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: tegra20-slink: Fix runtime PM imbalance on error
commit: faedcc17ad183acfa5d74758ebc4f21aef341f11
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2020-05-28 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 12:29 [PATCH] [v2] spi: tegra20-slink: Fix runtime PM imbalance on error Dinghao Liu
2020-05-28 13:07 ` Mark Brown [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=159067126729.55053.1525159932135385920.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=dinghao.liu@zju.edu.cn \
--cc=jonathanh@nvidia.com \
--cc=kjlu@umn.edu \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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 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).