| commit | 85ff87f76b0bffed9d5866ff17c7f4759e64b597 | [log] [tgz] |
|---|---|---|
| author | Tom Rini <trini@konsulko.com> | Sun Mar 30 09:10:57 2025 -0600 |
| committer | Tom Rini <trini@konsulko.com> | Sun Mar 30 09:11:07 2025 -0600 |
| tree | d1a588eb9f90acb777eff6be184f8dca36d504b2 | |
| parent | d6ff2d89e1004f76df3349af8d5efde6935894ef [diff] | |
| parent | 563f5044b88fb87ef2d18b6e70020ab4c580c02e [diff] |
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