linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Martinez Ruiz <alex@nowcomputing.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: f2fs backport and typo fix
Date: Mon, 28 Jan 2013 13:11:54 +0100	[thread overview]
Message-ID: <1359375114-6269-1-git-send-email-alex@nowcomputing.com> (raw)

Hi,

I recently ported f2fs to kernel 3.2, but I am not sure whether the changes are
all OK. If so, that could be useful to a number of projects, and I'd very much
appreciate any help in reviewing and looking for possible errors or omissions,
specially those related to VFS.

You can check the 3.2 kernel patches in http://github.com/nowcomputing/f2fs-backports.

Additionally, I just noticed a typo in f2fs options. Here's a patch for use with
git am --scissors.

Thanks,
  Alex

-- >8 --
From: Alejandro Martinez Ruiz <alex@nowcomputing.com>
Date: Fri, 25 Jan 2013 19:08:59 +0100
Subject: [PATCH] f2fs: fix disable_ext_identify option spelling

There is a typo in the ->show_options function for disable_ext_identify.
Fix it to match the spelling from the documentation.

Signed-off-by: Alejandro Martinez Ruiz <alex@nowcomputing.com>
---
 fs/f2fs/super.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 117ca2a..25656b6 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -198,7 +198,7 @@ static int f2fs_show_options(struct seq_file *seq, struct dentry *root)
 		seq_puts(seq, ",noacl");
 #endif
 	if (test_opt(sbi, DISABLE_EXT_IDENTIFY))
-		seq_puts(seq, ",disable_ext_indentify");
+		seq_puts(seq, ",disable_ext_identify");
 
 	seq_printf(seq, ",active_logs=%u", sbi->active_logs);
 
-- 
1.8.1.rc1.17.g75ed918


             reply	other threads:[~2013-01-28 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 12:11 Alejandro Martinez Ruiz [this message]
2013-01-29 11:43 ` f2fs backport and typo fix Jaegeuk Kim
2013-01-29 14:08   ` Alejandro Martinez

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=1359375114-6269-1-git-send-email-alex@nowcomputing.com \
    --to=alex@nowcomputing.com \
    --cc=jaegeuk.kim@samsung.com \
    --cc=linux-fsdevel@vger.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).