Merge patch series "Clarify DM_FLAG_PROBE_AFTER_BIND behaviour"
authorTom Rini <trini@konsulko.com>
Sun, 30 Mar 2025 15:10:57 +0000 (09:10 -0600)
committerTom Rini <trini@konsulko.com>
Sun, 30 Mar 2025 15:11:07 +0000 (09:11 -0600)
commitf1895bc1e71c18fb872e2fec40ff2310d6b4a0bb
treed1a588eb9f90acb777eff6be184f8dca36d504b2
parent5ca70325b64f760bf4190f206a0e88dda495e3d2
parent44450434ea9f0f2e0d8ddfd853f4990c1719b4aa
Merge patch series "Clarify DM_FLAG_PROBE_AFTER_BIND behaviour"

Caleb Connolly <caleb.connolly@linaro.org> says:

In Simon's series reworking autoprobe, a discussion came up about
DM_FLAG_PROBE_AFTER_BIND, specifically that it wasn't very clear where
this flag should be used.

This series implements my suggestions made there to clarify the use of
this flag, and fixup the two driver which erroneously apply it to their
driver struct (this does nothing).

Link: https://lore.kernel.org/u-boot/20241120153642.861633-1-sjg@chromium.org/
Link: https://lore.kernel.org/r/20250117-clarify-probe-after-bind-v1-0-273f046ce5dd@linaro.org