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:     lgirdwood@gmail.com, heiko@sntech.de, wens@kernel.org,
        tiwai@suse.com, perex@perex.cz
Cc:     linux-kernel@vger.kernel.org, wens@csie.org,
        alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org,
        linux-rockchip@lists.infradead.org, judyhsiao@chromium.org
In-Reply-To: <20220621185747.2782-1-wens@kernel.org>
References: <20220621185747.2782-1-wens@kernel.org>
Subject: Re: [PATCH] ASoC: rockchip: i2s: Fix crash on missing pinctrl
Message-Id: <165591900483.1405752.13168398437677956332.b4-ty@kernel.org>
Date:   Wed, 22 Jun 2022 18:30:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 22 Jun 2022 02:57:47 +0800, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai <wens@csie.org>
> 
> Commit 44f362c2cc6d ("ASoC: rockchip: i2s: switch BCLK to GPIO") added
> pinctrl lookups, but did not skip the lookup if there was no pinctrl
> device tied to the I2S controller. As a result, the lookup was done
> on an invalid pointer in such cases, causing a kernel panic.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: rockchip: i2s: Fix crash on missing pinctrl
      commit: c3b5fd7fbb698496461f280728b456d9927f22af

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