public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org,
	jefflexu@linux.alibaba.com, linux-kernel@vger.kernel.org,
	zhangwen@coolpad.com, Yue Hu <huyue2@coolpad.com>
Subject: Re: [PATCH] erofs: don't warn ztailpacking feature anymore
Date: Mon, 27 Feb 2023 17:52:48 +0800	[thread overview]
Message-ID: <20230227175248.00001dd9.zbestahu@gmail.com> (raw)
In-Reply-To: <4c6ada29-234f-623d-c4c6-1a98a678323b@linux.alibaba.com>

On Mon, 27 Feb 2023 17:42:40 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:

> On 2023/2/27 16:44, Yue Hu wrote:
> > From: Yue Hu <huyue2@coolpad.com>
> > 
> > The ztailpacking feature has been merged for a year, it has been mostly
> > stable now.
> > 
> > Signed-off-by: Yue Hu <huyue2@coolpad.com>  
> 
> Let's update erofs-utils as well?

Ok, I will update it later.

> 
> > ---
> >   fs/erofs/super.c | 2 --
> >   1 file changed, 2 deletions(-)
> > 
> > diff --git a/fs/erofs/super.c b/fs/erofs/super.c
> > index 19b1ae79cec4..733c22bcc3eb 100644
> > --- a/fs/erofs/super.c
> > +++ b/fs/erofs/super.c
> > @@ -417,8 +417,6 @@ static int erofs_read_superblock(struct super_block *sb)
> >   	/* handle multiple devices */
> >   	ret = erofs_scan_devices(sb, dsb);
> >   
> > -	if (erofs_sb_has_ztailpacking(sbi))
> > -		erofs_info(sb, "EXPERIMENTAL compressed inline data feature in use. Use at your own risk!");
> >   	if (erofs_is_fscache_mode(sb))
> >   		erofs_info(sb, "EXPERIMENTAL fscache-based on-demand read feature in use. Use at your own risk!");
> >   	if (erofs_sb_has_fragments(sbi))  


  reply	other threads:[~2023-02-27  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  8:44 [PATCH] erofs: don't warn ztailpacking feature anymore Yue Hu
2023-02-27  9:42 ` Gao Xiang
2023-02-27  9:52   ` Yue Hu [this message]
2023-03-03  0:53 ` Gao Xiang
2023-04-16 14:30 ` Chao Yu

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=20230227175248.00001dd9.zbestahu@gmail.com \
    --to=zbestahu@gmail.com \
    --cc=chao@kernel.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=huyue2@coolpad.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiang@kernel.org \
    --cc=zhangwen@coolpad.com \
    /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