diff options
author | Uwe Kleine-König <[email protected]> | 2022-06-10 23:12:55 +0200 |
---|---|---|
committer | Ulf Hansson <[email protected]> | 2022-07-12 12:25:38 +0200 |
commit | 397605c2d02abdcaba00e830fee0ee70a88b9456 (patch) | |
tree | 323007d8f56fcbbff82af2e8c65e90142c769d31 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 50699358222d004ad2b465c18b03d418b9b7fa90 (diff) |
mmc: dw_mmc: rockchip: 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