From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, clm@fb.com
Subject: [PATCH] btrfs: rename save_error_info to set_fs_error
Date: Wed, 16 Mar 2016 16:43:05 +0800 [thread overview]
Message-ID: <1458117788-840-1-git-send-email-anand.jain@oracle.com> (raw)
Actually save_error_info() is setting the FS state to error.
So rename is more appropriate.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
fs/btrfs/super.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 63a74303da9e..a11823b317ac 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -97,7 +97,7 @@ const char *btrfs_decode_error(int errno)
return errstr;
}
-static void save_error_info(struct btrfs_fs_info *fs_info)
+static void set_fs_error(struct btrfs_fs_info *fs_info)
{
/*
* today we only save the error info into ram. Long term we'll
@@ -171,7 +171,7 @@ void __btrfs_std_error(struct btrfs_fs_info *fs_info, const char *function,
#endif
/* Don't go through full error handling during mount */
- save_error_info(fs_info);
+ set_fs_error(fs_info);
if (sb->s_flags & MS_BORN)
btrfs_handle_error(fs_info);
}
--
2.7.0
next reply other threads:[~2016-03-16 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 8:43 Anand Jain [this message]
2016-03-16 8:43 ` [PATCH] btrfs: rename btrfs_std_error() to btrfs_handle_fs_error() Anand Jain
2016-03-16 10:14 ` David Sterba
2016-03-16 8:43 ` [PATCH] btrfs: remove unused function btrfs_assert() Anand Jain
2016-03-16 10:15 ` David Sterba
2016-03-16 8:43 ` [PATCH 5/5] btrfs: move error handling code together in ctree.h Anand Jain
2016-03-16 10:17 ` David Sterba
2016-03-16 10:05 ` [PATCH] btrfs: rename save_error_info to set_fs_error David Sterba
2016-03-16 13:42 ` Anand Jain
2016-03-16 15:49 ` David Sterba
2016-03-17 2:30 ` Anand Jain
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=1458117788-840-1-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.