From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mark Brown <broonie@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1 2/2] spi: tegra20-slink: Don't use resource-managed spi_register helper
Date: Sat, 31 Jul 2021 22:21:15 +0300 [thread overview]
Message-ID: <9a8bca7d-ad48-94e8-c37d-2259ced9953f@gmail.com> (raw)
In-Reply-To: <20210731191458.30535-2-digetx@gmail.com>
31.07.2021 22:14, Dmitry Osipenko пишет:
> Don't use resource-managed spi_register helper to correct the driver
> removal order and fix memory leak of spi_master that is never released.
The "memory leak" isn't correct, I now see where the devm variant
releases memory. I'll make v2 with a changed commit message.
prev parent reply other threads:[~2021-07-31 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 19:14 [PATCH v1 1/2] spi: tegra20-slink: Improve runtime PM usage Dmitry Osipenko
2021-07-31 19:14 ` [PATCH v1 2/2] spi: tegra20-slink: Don't use resource-managed spi_register helper Dmitry Osipenko
2021-07-31 19:21 ` 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=9a8bca7d-ad48-94e8-c37d-2259ced9953f@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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).