3 comments:
Patch Set #2, Line 9: If for some reason a value for fw_config cannot be located
What use case is this change trying to target? Is it the case where fw_config is unprovisioned?
Will add.
Patch Set #2, Line 12: fw_config_probe_nodefault
Under what circumstances would you use this function instead of fw_config_probe?
Will update.
When probing devices with fw_config, when the value is undefined or
unable to be located, all devices will be successfully probed, and
fw_config_probe will always return true.
Do we really need a Kconfig for this? I think it should be the default behavior i.e. […]
I could leave it out for now, that's true we won't use it right now, but it's pretty easy to add back in if someone else needs it.
To view, visit change 47956. To unsubscribe, or for help writing mail filters, visit settings.