linux-kernel - Re: (subset) [PATCH v6 00/12] platform/chrome: Introduce DT hardware prober

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <172547038191.87336.8695106953397068225.b4-ty@kernel.org>
Date: Wed, 04 Sep 2024 18:19:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Saravana Kannan <saravanak@...gle.com>, 
 Matthias Brugger <matthias.bgg@...il.com>, 
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, 
 Wolfram Sang <wsa@...nel.org>, Benson Leung <bleung@...omium.org>, 
 Tzung-Bi Shih <tzungbi@...nel.org>, Liam Girdwood <lgirdwood@...il.com>, 
 Chen-Yu Tsai <wenst@...omium.org>
Cc: chrome-platform@...ts.linux.dev, devicetree@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org, 
 linux-kernel@...r.kernel.org, Douglas Anderson <dianders@...omium.org>, 
 Johan Hovold <johan@...nel.org>, Jiri Kosina <jikos@...nel.org>, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
 linux-i2c@...r.kernel.org
Subject: Re: (subset) [PATCH v6 00/12] platform/chrome: Introduce DT
 hardware prober

On Wed, 04 Sep 2024 17:00:02 +0800, Chen-Yu Tsai wrote:
> This is v6 of my "of: Introduce hardware prober driver" [1] series.
> v6 mainly addresses comments from Andy.
> 
> v2 continued Doug's "of: device: Support 2nd sources of probeable but
> undiscoverable devices" [2] series, but follows the scheme suggested by
> Rob, marking all second source component device nodes as "fail-needs-probe",
> and having a hardware prober driver enable the one of them.
> 
> [...]

Applied to

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

Thanks!

[03/12] regulator: Move OF-specific regulator lookup code to of_regulator.c
        commit: b8c3255457147162cd713a319a8e2274335449b9

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