n interrupt
To fix this, re-start with the list-head after dropping the lock then
re-takeing it.
Reviewed-by: Frank Mori Hess
Tested-by: Frank Mori Hess
Signed-off-by: Qi Hou
---
drivers/dma/pl330.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/pl330.c b/
new one and the memory block
allocated before will a "ghost", then a kmemleak happened.
That the same "disabled" property being added to different nodes of device
tree would cause that kind of kmemleak overhead, at leat once.
To fix it, allocate the property dynamically, and del
new one and the memory block
allocated before will a "ghost", then a kmemleak happened.
That the same "disabled" property being added to different nodes of device
tree would cause that kind of kmemleak overhead, at leat once.
To fix it, allocate the property dynamically, and del
new one and the memory block
allocated before will a "ghost", then a kmemleak happened.
That the same "disabled" property being added to different nodes of device
tree would cause that kind of kmemleak overhead, at leat once.
To fix it, allocate the property dynamically, and del
er.
I consulted the technical reference of PL330 and the code of its driver,
but still not understanding the design completely.
So, what do you think, any ideas ?
Thanks your for time.
Reviewed-by: Zhang Xiao
Signed-off-by: Qi Hou
---
drivers/dma/pl330.c | 6 --
1 file changed, 4 insertions(+),
_off()
after that we clear hardirqs_enabled.
Signed-off-by: Qi Hou
---
kernel/locking/lockdep.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
index 577f026..e8b35e4 100644
--- a/kernel/locking/lockdep.c
+++ b/
dirqs_enabled. That will definitely cause an
"unannotated irqs-off" warning.
To fix this "unannotated irqs-off" warning, we must call trace_hardirqs_off()
after that we clear hardirqs_enabled.
Signed-off-by: Qi Hou
---
kernel/locking/lockdep.c | 4 ++--
1 file changed, 2 insertio
7 matches
Mail list logo
