From: Youling Tang <youling.tang@linux.dev>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
Youling Tang <tangyouling@kylinos.cn>
Subject: Re: [PATCH] bcachefs: Correct the description of the '--bucket=size' options
Date: Thu, 31 Oct 2024 16:05:44 +0800 [thread overview]
Message-ID: <da24a338-72ba-4148-be01-359d740a5aba@linux.dev> (raw)
In-Reply-To: <20241016015026.1555670-1-youling.tang@linux.dev>
Hi, Kent
Give you a friendly ping. 🙂
BTW, is the following patch needed?
[1]
https://lore.kernel.org/linux-bcachefs/20240709011134.79954-1-youling.tang@linux.dev/
[2]
https://lore.kernel.org/linux-bcachefs/20240924025350.3948674-1-youling.tang@linux.dev/
[3]
https://lore.kernel.org/linux-bcachefs/20240927084042.1516361-1-youling.tang@linux.dev/
[4]
https://lore.kernel.org/linux-bcachefs/20241016014911.1555607-1-youling.tang@linux.dev/
Thanks,
Youling.
On 2024/10/16 09:50, Youling Tang wrote:
> From: Youling Tang <tangyouling@kylinos.cn>
>
> Signed-off-by: Youling Tang <tangyouling@kylinos.cn>
> ---
> fs/bcachefs/opts.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/bcachefs/opts.h b/fs/bcachefs/opts.h
> index cb2e244a2429..92eae5636f2b 100644
> --- a/fs/bcachefs/opts.h
> +++ b/fs/bcachefs/opts.h
> @@ -487,7 +487,7 @@ enum fsck_err_opts {
> OPT_DEVICE, \
> OPT_UINT(0, S64_MAX), \
> BCH2_NO_SB_OPT, 0, \
> - "size", "Size of filesystem on device") \
> + "size", "Specifies the bucket size; must be greater than the btree node size")\
> x(durability, u8, \
> OPT_DEVICE|OPT_SB_FIELD_ONE_BIAS, \
> OPT_UINT(0, BCH_REPLICAS_MAX), \
next prev parent reply other threads:[~2024-10-31 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 1:50 [PATCH] bcachefs: Correct the description of the '--bucket=size' options Youling Tang
2024-10-31 8:05 ` Youling Tang [this message]
2024-11-07 21:47 ` Kent Overstreet
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=da24a338-72ba-4148-be01-359d740a5aba@linux.dev \
--to=youling.tang@linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tangyouling@kylinos.cn \
/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