From: Chao Yu <chao@kernel.org> To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH] f2fs: show sbi status in debugfs/f2f/sstatus Date: Sat, 31 Jul 2021 07:45:20 +0800 [thread overview] Message-ID: <f3331e35-9cfb-eb7b-8867-fb39f468c49d@kernel.org> (raw) In-Reply-To: <20210730190907.2072122-1-jaegeuk@kernel.org> On 2021/7/31 3:09, Jaegeuk Kim wrote: > We need to get sbi->s_flag to understand the current f2fs status as well. > One example is SBI_NEED_FSCK. Typo in patch title: "f2f/sstatus". Please note that there is a sysfs entry /sys/fs/f2fs/<devname/stat/sb_status. > > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> Reviewed-by: Chao Yu <chao@kernel.org> Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org> To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH] f2fs: show sbi status in debugfs/f2f/sstatus Date: Sat, 31 Jul 2021 07:45:20 +0800 [thread overview] Message-ID: <f3331e35-9cfb-eb7b-8867-fb39f468c49d@kernel.org> (raw) In-Reply-To: <20210730190907.2072122-1-jaegeuk@kernel.org> On 2021/7/31 3:09, Jaegeuk Kim wrote: > We need to get sbi->s_flag to understand the current f2fs status as well. > One example is SBI_NEED_FSCK. Typo in patch title: "f2f/sstatus". Please note that there is a sysfs entry /sys/fs/f2fs/<devname/stat/sb_status. > > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> Reviewed-by: Chao Yu <chao@kernel.org> Thanks, _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-07-30 23:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-30 19:09 [PATCH] f2fs: show sbi status in debugfs/f2f/sstatus Jaegeuk Kim 2021-07-30 19:09 ` [f2fs-dev] " Jaegeuk Kim 2021-07-30 23:45 ` Chao Yu [this message] 2021-07-30 23:45 ` Chao Yu 2021-07-31 0:44 ` Jaegeuk Kim 2021-07-31 0:44 ` Jaegeuk Kim
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=f3331e35-9cfb-eb7b-8867-fb39f468c49d@kernel.org \ --to=chao@kernel.org \ --cc=jaegeuk@kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-kernel@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: linkBe 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.