Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     thierry.reding@gmail.com, Zhang Shurong <zhang_shurong@foxmail.com>
Cc:     ldewangan@nvidia.com, jonathanh@nvidia.com, p.zabel@pengutronix.de,
        linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org,
        linux-kernel@vger.kernel.org
In-Reply-To: <tencent_71FC162D589E4788C2152AAC84CD8D5C6D06@qq.com>
References: <tencent_71FC162D589E4788C2152AAC84CD8D5C6D06@qq.com>
Subject: Re: [PATCH v2] spi: tegra20-sflash: fix to check return value of
 platform_get_irq() in tegra_sflash_probe()
Message-Id: <169039808617.123111.4823461346107082698.b4-ty@kernel.org>
Date:   Wed, 26 Jul 2023 20:01:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Sat, 22 Jul 2023 23:49:09 +0800, Zhang Shurong wrote:
> The platform_get_irq might be failed and return a negative result. So
> there should have an error handling code.
> 
> Fixed this by adding an error handling code.
> 
> 

Applied to

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

Thanks!

[1/1] spi: tegra20-sflash: fix to check return value of platform_get_irq() in tegra_sflash_probe()
      commit: 29a449e765ff70a5bd533be94babb6d36985d096

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