FYI, we noticed the below changes on

https://github.com/0day-ci/linux Alan-Tull/of-add-pre-operation-notifications/20160225-063254
commit 681c3cb0e4d77a0eed48269e2db81bffb97e6604 ("of: add pre-operation notifications")


[   15.344947] 
[   15.345268] ======================================================
[   15.345268] ======================================================
[   15.346491] [ INFO: possible circular locking dependency detected ]
[   15.346491] [ INFO: possible circular locking dependency detected ]
[   15.347758] 4.5.0-rc3-00013-g681c3cb #2 Not tainted
[   15.347758] 4.5.0-rc3-00013-g681c3cb #2 Not tainted
[   15.348734] -------------------------------------------------------
[   15.348734] -------------------------------------------------------
[   15.349977] swapper/0/1 is trying to acquire lock:
[   15.349977] swapper/0/1 is trying to acquire lock:
[   15.350953]  (
[   15.350953]  (of_mutexof_mutex){+.+.+.}){+.+.+.}, at: , at: [<816768c2>] of_device_uevent+0x102/0x1a0
[<816768c2>] of_device_uevent+0x102/0x1a0
[   15.352460] 
[   15.352460] but task is already holding lock:
[   15.352460] 
[   15.352460] but task is already holding lock:
[   15.353648]  (
[   15.353648]  ((of_reconfig_chain).rwsem(of_reconfig_chain).rwsem){.+.+.+}){.+.+.+}, at: , at: [<8106db1b>] __blocking_notifier_call_chain+0x1b/0x60
[<8106db1b>] __blocking_notifier_call_chain+0x1b/0x60
[   15.355651] 
[   15.355651] which lock already depends on the new lock.
[   15.355651] 
[   15.355651] 
[   15.355651] which lock already depends on the new lock.
[   15.355651] 
[   15.357273] 
[   15.357273] the existing dependency chain (in reverse order) is:


Thanks,
Kernel Test Robot