From: Mark Brown <broonie@kernel.org>
To: Purushothama Siddaiah <psiddaiah@mvista.com>,
Corey Minyard <cminyard@mvista.com>,
Lars Pedersen <lapeddk@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: omap2-mcspi: Correctly handle devm_clk_get_optional() errors
Date: Tue, 21 Jan 2025 15:05:36 +0000 [thread overview]
Message-ID: <173747193673.38422.16913567747416591096.b4-ty@kernel.org> (raw)
In-Reply-To: <20250117-spi-fix-omap2-optional-v1-1-e77d4ac6db6e@kernel.org>
On Fri, 17 Jan 2025 16:16:03 +0000, Mark Brown wrote:
> devm_clk_get_optional() returns NULL for missing clocks and a PTR_ERR()
> if there is a clock but we fail to get it, but currently we only handle
> the latter case and do so as though the clock was missing. If we get an
> error back we should handle that as an error since the clock exists but
> we failed to get it, if we get NULL then the clock doesn't exist and we
> should handle that.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: omap2-mcspi: Correctly handle devm_clk_get_optional() errors
commit: a07eb4f67ed085f32002a1af2b6073546d67de3f
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:[~2025-01-21 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 16:16 Mark Brown
2025-01-21 12:00 ` Lars Pedersen
2025-01-21 15:05 ` 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=173747193673.38422.16913567747416591096.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=cminyard@mvista.com \
--cc=lapeddk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=psiddaiah@mvista.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
all inboxes | Powered by JetHome®