[v2,0/2] Match dtat improvements for pv880x0 regulator driver

Message ID 20230828172417.113631-1-biju.das.jz@bp.renesas.com
Headers
Series Match dtat improvements for pv880x0 regulator driver |

Message

Biju Das Aug. 28, 2023, 5:24 p.m. UTC
  This patch series aims to add match data improvements for pv880x0
regulator driver.

This patch is only compile tested.

v1->v2:
 * Moved OF/ID tables close to the user
 * Removed trailing comma in the terminator entry for OF/ID tables.
 * Created patc#2 for dropping CONFIG_OF ifdeffery.

Biju Das (2):
  regulator: pv880x0: Simplify probe()
  regulator: pv880x0: Drop ifdeffery

 drivers/regulator/pv88080-regulator.c | 58 ++++++++-------------------
 1 file changed, 17 insertions(+), 41 deletions(-)
  

Comments

Mark Brown Sept. 12, 2023, 1:29 p.m. UTC | #1
On Mon, 28 Aug 2023 18:24:15 +0100, Biju Das wrote:
> This patch series aims to add match data improvements for pv880x0
> regulator driver.
> 
> This patch is only compile tested.
> 
> v1->v2:
>  * Moved OF/ID tables close to the user
>  * Removed trailing comma in the terminator entry for OF/ID tables.
>  * Created patc#2 for dropping CONFIG_OF ifdeffery.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: pv880x0: Simplify probe()
      commit: 1b4daf643a3a21cff4bcad5b799960d5a0673d11
[2/2] regulator: pv880x0: Drop CONFIG_OF ifdeffery
      (no commit info)

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