From: Mark Brown <broonie@kernel.org>
To: alexander.sverdlin@siemens.com, carlos.song@nxp.com
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, haibo.chen@nxp.com, jun.li@nxp.com,
linux-imx@nxp.com
Subject: Re: [PATCH] spi: spi-fsl-lpspi: remove redundant spi_controller_put call
Date: Wed, 03 Apr 2024 14:32:43 +0100 [thread overview]
Message-ID: <171215116351.907765.4790730663496497496.b4-ty@kernel.org> (raw)
In-Reply-To: <20240403084029.2000544-1-carlos.song@nxp.com>
On Wed, 03 Apr 2024 16:40:29 +0800, carlos.song@nxp.com wrote:
> devm_spi_alloc_controller will allocate an SPI controller and
> automatically release a reference on it when dev is unbound from
> its driver. It doesn't need to call spi_controller_put explicitly
> to put the reference when lpspi driver failed initialization.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-fsl-lpspi: remove redundant spi_controller_put call
commit: bff892acf79cec531da6cb21c50980a584ce1476
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:[~2024-04-03 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 8:40 [PATCH] spi: spi-fsl-lpspi: remove redundant spi_controller_put call carlos.song
2024-04-03 8:51 ` Sverdlin, Alexander
2024-04-03 10:09 ` Carlos Song
2024-04-03 13:32 ` 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=171215116351.907765.4790730663496497496.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=carlos.song@nxp.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).