linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Li Guifu <blucerlee@gmail.com>
To: Gao Xiang <hsiangkao@aol.com>,
	linux-erofs@lists.ozlabs.org, bluce.liguifu@huawei.com,
	miaoxie@huawei.com, fangwei1@huawei.com
Subject: Re: [PATCH 3/3] erofs-utils: keep up with in-kernel ondisk format naming
Date: Tue, 17 Sep 2019 23:15:51 +0800	[thread overview]
Message-ID: <e802ed36-90ee-568f-6233-f9bdee6d2739@gmail.com> (raw)
In-Reply-To: <20190917054913.24187-3-hsiangkao@aol.com>



在 2019/9/17 13:49, Gao Xiang via Linux-erofs 写道:
> From: Gao Xiang <gaoxiang25@huawei.com>
> 
> This patch adapts erofs-utils to the latest kernel ondisk definitions,
> especially the following kernel commits:
> 
> 4b66eb51d2c4 erofs: remove all the byte offset comments
> 60a49ba8fee1 erofs: on-disk format should have explicitly assigned numbers
> b6796abd3cc1 erofs: some macros are much more readable as a function
> ed34aa4a8a7d erofs: kill __packed for on-disk structures
> c39747f770be erofs: update erofs_inode_is_data_compressed helper
> 426a930891cf erofs: use feature_incompat rather than requirements
> 8a76568225de erofs: better naming for erofs inode related stuffs
> ea559e7b8451 erofs: update erofs_fs.h comments
> 
> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
> ---
It looks good.
Reviewed-by: Li Guifu <blucerlee@gmail.com>
Thanks,

  reply	other threads:[~2019-09-17 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190917054913.24187-1-hsiangkao.ref@aol.com>
2019-09-17  5:49 ` [PATCH 1/3] erofs-utils: complete special file support Gao Xiang via Linux-erofs
2019-09-17  5:49   ` [PATCH 2/3] erofs-utils: resize image to the correct size Gao Xiang via Linux-erofs
2019-09-17 15:15     ` Li Guifu
2019-09-17  5:49   ` [PATCH 3/3] erofs-utils: keep up with in-kernel ondisk format naming Gao Xiang via Linux-erofs
2019-09-17 15:15     ` Li Guifu [this message]
2019-09-17 15:15   ` [PATCH 1/3] erofs-utils: complete special file support Li Guifu

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=e802ed36-90ee-568f-6233-f9bdee6d2739@gmail.com \
    --to=blucerlee@gmail.com \
    --cc=bluce.liguifu@huawei.com \
    --cc=fangwei1@huawei.com \
    --cc=hsiangkao@aol.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=miaoxie@huawei.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).