linux-kernel - Re: [PATCH v3 0/2] Match data improvements for pv880x0 regulator driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <169452537465.2406132.16400593952945851153.b4-ty@kernel.org>
Date:   Tue, 12 Sep 2023 14:29:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Biju Das <biju.das.jz@...renesas.com>
Cc:     linux-kernel@...r.kernel.org, Biju Das <biju.das.au@...il.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v3 0/2] Match data improvements for pv880x0 regulator
 driver

On Sun, 03 Sep 2023 17:48:30 +0100, Biju Das wrote:
> This patch series aims to add match data improvements for pv880x0
> regulator driver.
> 
> This patch is only compile tested.
> 
> v2->v3:
>  * Swapped the patch#1 and patch#2
>  * Removed trailing comma in the terminator entry for OF/ID table.
>  * Updated commit description of patch#1
>  * Restored OF table position in patch#1 and moved OF tables close to the
>    user in patch#2.
>  * Dropped extra space from OF table entry.
> v1->v2:
>  * Moved OF/ID tables close to the user
>  * Removed trailing comma in the terminator entry for OF/ID tables.
>  * Created patch#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: Drop ifdeffery
      commit: c187b8f87d553cc124c568ecc010a8bf73cf745f
[2/2] regulator: pv880x0: Simplify probe()
      commit: 1b4daf643a3a21cff4bcad5b799960d5a0673d11

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