From: Zheng Lv <lv.zheng.2015@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: hirofumi@mail.parknet.co.jp, Zheng Lv <lv.zheng.2015@gmail.com>,
trivial@kernel.org
Subject: [PATCH] fat: fix typo s/supeblock/superblock/
Date: Mon, 20 Jun 2016 23:51:29 -0400 [thread overview]
Message-ID: <1466481089-27097-1-git-send-email-lv.zheng.2015@gmail.com> (raw)
Signed-off-by: Zheng Lv <lv.zheng.2015@gmail.com>
Cc: trivial@kernel.org
---
fs/fat/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fat/inode.c b/fs/fat/inode.c
index 3bcf579..b902c89 100644
--- a/fs/fat/inode.c
+++ b/fs/fat/inode.c
@@ -1589,7 +1589,7 @@ int fat_fill_super(struct super_block *sb, void *data, int silent, int isvfat,
/*
* GFP_KERNEL is ok here, because while we do hold the
- * supeblock lock, memory pressure can't call back into
+ * superblock lock, memory pressure can't call back into
* the filesystem, since we're only just about to mount
* it and have no inodes etc active!
*/
--
2.7.4
next reply other threads:[~2016-06-21 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 3:51 Zheng Lv [this message]
2016-06-22 20:34 ` [PATCH] fat: fix typo s/supeblock/superblock/ OGAWA Hirofumi
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=1466481089-27097-1-git-send-email-lv.zheng.2015@gmail.com \
--to=lv.zheng.2015@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).