From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use f2fs_hw_is_readonly() instead of bdev_read_only()
Date: Tue, 11 Apr 2023 17:00:19 +0000 [thread overview]
Message-ID: <168123241984.4928.10498593969347479726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410021722.1836433-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 10 Apr 2023 10:17:22 +0800 you wrote:
> f2fs has supported multi-device feature, to check devices' rw status,
> it should use f2fs_hw_is_readonly() rather than bdev_read_only(), fix
> it.
>
> Meanwhile, it removes f2fs_hw_is_readonly() check condition in:
> - f2fs_write_checkpoint()
> - f2fs_convert_inline_inode()
> As it has checked f2fs_readonly() condition, and if f2fs' devices
> were readonly, f2fs_readonly() must be true.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: use f2fs_hw_is_readonly() instead of bdev_read_only()
https://git.kernel.org/jaegeuk/f2fs/c/68f0453dabdb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use f2fs_hw_is_readonly() instead of bdev_read_only()
Date: Tue, 11 Apr 2023 17:00:19 +0000 [thread overview]
Message-ID: <168123241984.4928.10498593969347479726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410021722.1836433-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 10 Apr 2023 10:17:22 +0800 you wrote:
> f2fs has supported multi-device feature, to check devices' rw status,
> it should use f2fs_hw_is_readonly() rather than bdev_read_only(), fix
> it.
>
> Meanwhile, it removes f2fs_hw_is_readonly() check condition in:
> - f2fs_write_checkpoint()
> - f2fs_convert_inline_inode()
> As it has checked f2fs_readonly() condition, and if f2fs' devices
> were readonly, f2fs_readonly() must be true.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: use f2fs_hw_is_readonly() instead of bdev_read_only()
https://git.kernel.org/jaegeuk/f2fs/c/68f0453dabdb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-11 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 2:17 [f2fs-dev] [PATCH] f2fs: use f2fs_hw_is_readonly() instead of bdev_read_only() Chao Yu
2023-04-10 2:17 ` Chao Yu
2023-04-11 17:00 ` patchwork-bot+f2fs [this message]
2023-04-11 17:00 ` [f2fs-dev] " patchwork-bot+f2fs
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=168123241984.4928.10498593969347479726.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=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: 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.