diff options
author | Martin Blumenstingl <[email protected]> | 2019-04-12 00:00:56 +0200 |
---|---|---|
committer | Miquel Raynal <[email protected]> | 2019-04-18 08:54:07 +0200 |
commit | 39e01956e2f70ff9f0e97db1a69c9847aa1d5d8b (patch) | |
tree | dcdaac6911fca468ab2ae83eaae41ef0da4da4c0 /tools/perf/scripts/python/compaction-times.py | |
parent | c96ffedf8a2f91c9124012ec4eef42a3da01d08b (diff) |
mtd: rawnand: meson: only initialize the RB completion once
Documentation/scheduler/completion.txt states:
Calling init_completion() on the same completion object twice is
most likely a bug as it re-initializes the queue to an empty queue and
enqueued tasks could get "lost" - use reinit_completion() in that case,
but be aware of other races.
Initialize nfc->completion in meson_nfc_probe using init_completion and
change the call in meson_nfc_queue_rb to reinit_completion so the logic
matches what the documentation suggests.
Signed-off-by: Martin Blumenstingl <[email protected]>
Tested-by:Liang Yang <[email protected]>
Acked-by: Liang Yang <[email protected]>
Tested-by:Liang Yang <[email protected]>
Acked-by: Liang Yang <[email protected]>
Signed-off-by: Miquel Raynal <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/compaction-times.py')
0 files changed, 0 insertions, 0 deletions