[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163962127796.2075461.6086847444730016805.b4-ty@kernel.org>
Date: Thu, 16 Dec 2021 02:21:17 +0000
From: Mark Brown <broonie@...nel.org>
To: Wolfram Sang <wsa@...-dreams.de>, Stephen Boyd <sboyd@...nel.org>,
Daniel Scally <djrscally@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Hans de Goede <hdegoede@...hat.com>,
Mark Gross <markgross@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Liam Girdwood <lgirdwood@...il.com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Andy Shevchenko <andy@...radead.org>
Cc: Len Brown <lenb@...nel.org>, Kate Hsuan <hpa@...hat.com>,
linux-kernel@...r.kernel.org,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
linux-clk@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-media@...r.kernel.org, platform-driver-x86@...r.kernel.org
Subject: Re: (subset) [PATCH v7 00/14] Add support for X86/ACPI camera sensor/PMIC setup with clk and regulator platform data
On Fri, 3 Dec 2021 11:28:43 +0100, Hans de Goede wrote:
> Here is v7 of my patch-set adding support for camera sensor connected to a
> TPS68470 PMIC on x86/ACPI devices.
>
> Changes in v7:
> - Drop "platform/x86: int3472: Enable I2c daisy chain" this workaround is
> no longer necessary (the regulator code now takes care of this)
> - Fix using PTR_ERR(data->clk) instead of PTR_ERR(rdev) to log an error
> code in "regulator: Introduce tps68470-regulator driver"
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[05/14] regulator: Introduce tps68470-regulator driver
commit: 0fc31d8f1a8ad17224f6423e3ed6234507375d48
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