All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Zhang Qilong <zhangqilong3@huawei.com>
Cc: ldewangan@nvidia.com, jonathanh@nvidia.com,
	thierry.reding@gmail.com, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: tegra20-slink: fix reference leak in slink ops of tegra20
Date: Mon, 09 Nov 2020 19:48:17 +0000	[thread overview]
Message-ID: <160495129750.49337.7912431338508137838.b4-ty@kernel.org> (raw)
In-Reply-To: <20201103141345.6188-1-zhangqilong3@huawei.com>

On Tue, 3 Nov 2020 22:13:45 +0800, Zhang Qilong wrote:
> pm_runtime_get_sync will increment pm usage counter even it
> failed. Forgetting to pm_runtime_put_noidle will result in
> reference leak in two callers(tegra_slink_setup and
> tegra_slink_resume), so we should fix it.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: tegra20-slink: fix reference leak in slink ops of tegra20
      commit: 763eab7074f6e71babd85d796156f05a675f9510

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

      reply	other threads:[~2020-11-09 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 14:13 [PATCH] spi: tegra20-slink: fix reference leak in slink ops of tegra20 Zhang Qilong
2020-11-09 19:48 ` 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=160495129750.49337.7912431338508137838.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-spi@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=zhangqilong3@huawei.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.