Subject: [merged] aio-fix-wrong-comment-in-aio_complete.patch removed from -mm tree
To: tangchen@xxxxxxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Mon, 08 Jul 2013 12:37:18 -0700
The patch titled
Subject: aio: fix wrong comment in aio_complete()
has been removed from the -mm tree. Its filename was
aio-fix-wrong-comment-in-aio_complete.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Tang Chen <tangchen@xxxxxxxxxxxxxx>
Subject: aio: fix wrong comment in aio_complete()
ctx->ctx_lock should be ctx->completion_lock.
Signed-off-by: Tang Chen <tangchen@xxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/aio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/aio.c~aio-fix-wrong-comment-in-aio_complete fs/aio.c
--- a/fs/aio.c~aio-fix-wrong-comment-in-aio_complete
+++ a/fs/aio.c
@@ -625,7 +625,7 @@ void aio_complete(struct kiocb *iocb, lo
/*
* Add a completion event to the ring buffer. Must be done holding
- * ctx->ctx_lock to prevent other code from messing with the tail
+ * ctx->completion_lock to prevent other code from messing with the tail
* pointer since we might be called from irq context.
*/
spin_lock_irqsave(&ctx->completion_lock, flags);
_
Patches currently in -mm which might be from tangchen@xxxxxxxxxxxxxx are
origin.patch
page-migration-fix-wrong-comment-in-address_space_operationsmigratepage.patch
mm-memblockc-fix-wrong-comment-in-__next_free_mem_range.patch
mm-memory_hotplugc-fix-a-comment-typo-in-register_page_bootmem_info_node.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
