[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169107882741.87002.3144423833085038986.b4-ty@kernel.org>
Date: Thu, 03 Aug 2023 17:07:07 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
Zhu Wang <wangzhu9@...wei.com>
Subject: Re: [PATCH -next] spi: fsl-spi: Do not check 0 for
platform_get_irq()
On Thu, 03 Aug 2023 16:39:44 +0800, Zhu Wang wrote:
> Since platform_get_irq() never returned zero, so it need not to check
> whether it returned zero, and we use the return error code of
> platform_get_irq() to replace the current return error code, for that
> platform_get_irq() may return -EINVAL or -ENXIO.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: fsl-spi: Do not check 0 for platform_get_irq()
commit: d8736266ae960504110e812994f555bf7cb8740c
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
Powered by blists - more mailing lists