[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169447665810.2387538.3521988123719858959.b4-ty@kernel.org>
Date: Tue, 12 Sep 2023 00:57:38 +0100
From: Mark Brown <broonie@...nel.org>
To: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Biju Das <biju.das.jz@...renesas.com>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v3 0/2] Match data improvements for ak4642 driver
On Thu, 31 Aug 2023 21:47:32 +0100, Biju Das wrote:
> This patch series aims to add match data improvements for ak4642 driver.
>
> This patch series is only compile tested.
>
> v2->v3:
> * Patch#1 for cleanups and patch#2 for simplifying probe()
> * Replace local variable np with dev_fwnode()
> * Replace dev_err()->dev_err_probe().
> * Remove comma in the terminator entry for OF table.
> * Drop a space in the terminator entry for ID table.
> v1->v2:
> * Removed forward declaration ak4642_of_match and ak4642_i2c_id.
> * Restored error EINVAL.
> * Used dev_fwnode() and replaced dev->of_node.
> * Removed comma in the terminator entry.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: ak4642: Minor cleanups in probe()
commit: a157d07d029be5b72ee3bce3ac44dab7b967bc9b
[2/2] ASoC: ak4642: Simplify probe()
commit: d9e6a80a2c7bea4cc2edc87fa43b876a64b13074
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