diff options
author | Uwe Kleine-König <[email protected]> | 2022-06-10 23:12:53 +0200 |
---|---|---|
committer | Ulf Hansson <[email protected]> | 2022-07-12 12:25:37 +0200 |
commit | 68eab5176c71fe03ff37723a1c5cf20c26b06a99 (patch) | |
tree | 1c536b56f152c5a62bb38dcfb398e96310f8955a /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | c3c0ed75ffbff5c70667030b5139bbb75b0a30f5 (diff) |
mmc: dw_mmc: exynos: Obviously always return success in remove callback
dw_mci_pltfm_remove() returns 0 unconditionally and returning an error
in a platform remove callback isn't very sensible. (The only effect of
the latter is that the device core emits a generic warning and then
removes the device anyhow.)
So return 0 unconditionally to make it obvious there is no error
forwarded to the upper layers.
This is a preparation for making platform remove callbacks return void.
Signed-off-by: Uwe Kleine-König <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions