The patch titled Subject: nbd: fix sparse warning has been added to the -mm tree. Its filename is nbd-fix-sparse-warning.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Alex Elder <elder@xxxxxxxxxxx> Subject: nbd: fix sparse warning I just fixed this in "drivers/block/rbd.c" and I noticed that "drivers/block/nbd.c" has the same problem. Fix a warning issued by sparse by adding some lockdep annotations to indicate the queue lock gets dropped (because it's held when do_nbd_request() is called) and re-acquired within the function. Signed-off-by: Alex Elder <elder@xxxxxxxxxxx> Cc: Paul Clements <paul.clements@xxxxxxxxxxxx> Cc: Paul Clements <paul.clements@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/block/nbd.c | 1 + 1 file changed, 1 insertion(+) diff -puN drivers/block/nbd.c~nbd-fix-sparse-warning drivers/block/nbd.c --- a/drivers/block/nbd.c~nbd-fix-sparse-warning +++ a/drivers/block/nbd.c @@ -564,6 +564,7 @@ static int nbd_thread(void *data) */ static void do_nbd_request(struct request_queue *q) + __releases(q->queue_lock) __acquires(q->queue_lock) { struct request *req; _ Patches currently in -mm which might be from elder@xxxxxxxxxxx are origin.patch linux-next.patch nbd-fix-sparse-warning.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html