From: Tang Chen <tangchen@cn.fujitsu.com>
To: bcrl@kvack.org, akpm@linux-foundation.org, hpa@zytor.com,
trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/5] aio: Fix wrong comment in aio_complete()
Date: Thu, 20 Jun 2013 18:10:21 +0800 [thread overview]
Message-ID: <1371723023-4060-4-git-send-email-tangchen@cn.fujitsu.com> (raw)
In-Reply-To: <1371723023-4060-1-git-send-email-tangchen@cn.fujitsu.com>
ctx->ctx_lock should be ctx->completion_lock.
Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
---
fs/aio.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 2bbcacf..e4a01fa 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -623,7 +623,7 @@ void aio_complete(struct kiocb *iocb, long res, long res2)
/*
* 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);
--
1.7.1
next prev parent reply other threads:[~2013-06-20 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 10:10 [PATCH 0/5] Fix some wrong comments Tang Chen
2013-06-20 10:10 ` [PATCH 1/5] page_isolation: Fix a comment typo in test_pages_isolated() Tang Chen
2013-06-20 13:17 ` Zhang Yanfei
2013-06-21 1:12 ` Tang Chen
2013-06-20 10:10 ` [PATCH 2/5] page_migrate: Fix wrong comment in address_space_operations->migratepage() Tang Chen
2013-08-20 11:02 ` Jiri Kosina
2013-08-20 11:05 ` Tang Chen
2013-06-20 10:10 ` Tang Chen [this message]
2013-06-20 10:10 ` [PATCH 4/5] memblock: Fix wrong comment in __next_free_mem_range() Tang Chen
2013-06-20 10:10 ` [PATCH 5/5] bootmem, numa: Fix a comment typo in register_page_bootmem_info_node() Tang Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1371723023-4060-4-git-send-email-tangchen@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®