[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168916243503.46574.8648492910653154560.b4-ty@kernel.org>
Date: Wed, 12 Jul 2023 12:47:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Mauro Carvalho Chehab <mchehab@...nel.org>,
Hans Verkuil <hverkuil-cisco@...all.nl>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
David Lin <CTLIN0@...oton.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
alsa-devel@...a-project.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Jonathan Corbet <corbet@....net>, Antti Palosaari <crope@....fi>,
Sergey Kozlov <serjk@...up.ru>, Abylay Ospan <aospan@...up.ru>,
Yasunari Takiguchi <Yasunari.Takiguchi@...y.com>,
Michael Krufky <mkrufky@...uxtv.org>,
Matthias Schwarzott <zzam@...too.org>,
Akihiro Tsukada <tskd08@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH v2 0/4] ASoC: remove copy of intlog10()
On Mon, 03 Jul 2023 16:52:07 +0300, Andy Shevchenko wrote:
> The first three patches moves intlog10() to be available in entire
> kernel. The last one removes copy of it in one driver. Besides already
> good Lines of Code (LoC) statistics the upcoming users, if any, can
> utilize the exported functions.
>
> The series can be routed via ASoC tree (as Mauro suggested).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] lib/math: Move dvb_math.c into lib/math/int_log.c
commit: f97fa3dcb2db02013e6904c032a1d2d45707ee40
[2/4] lib/math/int_log: Use ARRAY_SIZE(logtable) where makes sense
commit: 08f6a14b2d376e96cb7166694193ec3c3a496d25
[3/4] lib/math/int_log: Replace LGPL-2.1-or-later boilerplate with SPDX identifier
commit: 9ab04d7ed8bdd395b0617a1647dd475681f99151
[4/4] ASoC: nau8825: Replace copied'n'pasted intlog10()
commit: a04616321f50bc389cd8d19a6d300d3c3f1be77b
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