linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Robin Hsu <robinh3123@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] sload.f2fs: Reword "IMMUTABLE" in strings/comments
Date: Tue, 22 Jun 2021 08:10:15 -0700	[thread overview]
Message-ID: <YNH9V+gHPHkji1ah@google.com> (raw)
In-Reply-To: <20210622133357.GA1003@bug>

On 06/22, Pavel Machek wrote:
> Hi!
> 
> > Since the IMMUTABLE flag for compression is now changed
> > to F2FS_COMPRESS_RELEASED, some 'IMMUTABLE' words should be changed too:
> > 	1. sload help page
> > 	2. inline comments
> > 
> > Signed-off-by: Robin Hsu <robinhsu@google.com>
> 
> > @@ -650,7 +651,7 @@ void f2fs_parse_options(int argc, char *argv[])
> >  				}
> >  				c.compress.min_blocks = val;
> >  				break;
> > -			case 'r': /* compress file to set IMMUTABLE */
> > +			case 'r': /* for setting F2FS_COMOPRESS_RELEASE */
> 
> Typo.

Ah, fixed. Thank you~

> 
> Best regards,
> 									Pavel
> 
> -- 
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2021-06-22 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  7:31 [f2fs-dev] [PATCH] sload.f2fs: Reword "IMMUTABLE" in strings/comments Robin Hsu
2021-06-22 13:33 ` Pavel Machek
2021-06-22 15:10   ` Jaegeuk Kim [this message]

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=YNH9V+gHPHkji1ah@google.com \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robinh3123@gmail.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;
as well as URLs for NNTP newsgroup(s).