[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <162913223312.13582.10888100799475599538.b4-ty@kernel.org>
Date: Mon, 16 Aug 2021 18:04:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>,
Aakash Hemadri <aakashhemadri123@...il.com>
Cc: Mark Brown <broonie@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
alsa-devel@...a-project.org, Takashi Iwai <tiwai@...e.com>,
linux-tegra@...r.kernel.org, Bjorn Helgaas <bjorn@...gaas.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Jawoslav Kysela <perex@...ex.cz>,
Thierry Reding <thierry.reding@...il.com>,
Shuah Khan <skhan@...uxfoundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: tegra: Use of_device_get_match_data
On Sun, 15 Aug 2021 01:42:17 +0530, Aakash Hemadri wrote:
> Prefer `of_device_get_match_data` over `of_match_device`. This patch
> replaces of_match_device with of_device_get_match_data.
>
> This patch series will apply cleanly on for-next
>
> Aakash Hemadri (2):
> ASoC: tegra30: ahub: Use of_device_get_match_data
> ASoC: tegra30: i2s: Use of_device_get_match_data
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: tegra30: ahub: Use of_device_get_match_data
commit: 80165bb8043391f4ef4916bde947a4d805a54aa6
[2/2] ASoC: tegra30: i2s: Use of_device_get_match_data
commit: 356b94a32a75203616e5a7c3cd2b19101bc87086
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