diff options
| author | Dan Carpenter <[email protected]> | 2020-06-09 13:46:42 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2020-07-10 14:15:55 +0200 |
| commit | 7ae731a8441d70e5fb6144422a675bf1b2d6ace9 (patch) | |
| tree | e6ab0a16c839a4caa2a3387ee469e4704b66a333 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 35bd8c07db2ce8fd2834ef866240613a4ef982e7 (diff) | |
lib: devres: add a comment about the devm_of_iomap() function
We recently introduced a bug when we tried to convert of_iomap() to
devm_of_iomap(). The problem was that there were two drivers mapping
the same io region. The first driver was using of_iomap() and the
second driver was using devm_of_iomap() and the kernel booted fine.
When we converted the first drive to use devm_of_iomap() then the second
driver failed with -EBUSY and the kernel couldn't boot.
Let's add a comment to prevent this sort of mistake in the future.
Signed-off-by: Dan Carpenter <[email protected]>
Acked-by: Arnd Bergmann <[email protected]>
Link: https://lore.kernel.org/r/20200609104642.GA43074@mwanda
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions