diff options
| author | David Härdeman <[email protected]> | 2017-04-27 17:34:08 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2017-06-13 13:55:01 -0300 |
| commit | 18726a349de262f5bf03fab73fc7c46e79e6c41e (patch) | |
| tree | 667f4a4bf068256f613dcc001891266bea45c295 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | f56928abaa6d73613d21f0cdcb7fd0b7f339b5bd (diff) | |
[media] rc-core: cleanup rc_register_device pt2
Now that rc_register_device() is reorganised, the dev->initialized
hack can be removed. Any driver which calls rc_register_device()
must be prepared for the device to go live immediately.
The dev->initialized commits that are relevant are commit c73bbaa4ec3e
("[media] rc-core: don't lock device at rc_register_device()") and
commit 08aeb7c9a42a ("[media] rc: add locking to fix register/show race").
The original problem was that show_protocols() would access
dev->rc_map.* and various other bits which are now properly
initialized before device_add() is called.
At the same time, remove the bogus "device is being removed" check.
Signed-off-by: David Härdeman <[email protected]>
Signed-off-by: Sean Young <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions