From: chao@kernel.org (Chao Yu)
Subject: [PATCH v3 04/10] staging: erofs: fix a missing endian conversion
Date: Sat, 11 Aug 2018 22:31:00 +0800 [thread overview]
Message-ID: <fb551278-5e36-8a3c-e35b-6ffa2112cfd6@kernel.org> (raw)
In-Reply-To: <1533931838-47642-4-git-send-email-gaoxiang25@huawei.com>
On 2018/8/11 4:10, Gao Xiang wrote:
> This patch fixes a missing endian conversion in
> vle_get_logical_extent_head.
>
> Signed-off-by: Gao Xiang <gaoxiang25 at huawei.com>
Reviewed-by: Chao Yu <yuchao0 at huawei.com>
Thanks,
next prev parent reply other threads:[~2018-08-11 14:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 20:10 [PATCH RESEND 01/10] staging: erofs: cleanup z_erofs_vle_work_{lookup, register} Gao Xiang
2018-08-10 20:10 ` [PATCH RESEND 02/10] staging: erofs: rearrange vle clustertype definitions Gao Xiang
2018-08-10 20:10 ` [PATCH v2 03/10] staging: erofs: fix vle_decompressed_index_clusterofs Gao Xiang
2018-08-11 14:18 ` Chao Yu
2018-08-10 20:10 ` [PATCH v3 04/10] staging: erofs: fix a missing endian conversion Gao Xiang
2018-08-11 14:31 ` Chao Yu [this message]
2018-08-10 20:10 ` [PREVIEW] [PATCH v3 05/10] staging: erofs: fix integer overflow on 32-bit platform Gao Xiang
2018-08-11 14:32 ` Chao Yu
2018-08-12 7:54 ` [PREVIEW] [PATCH v4 " Gao Xiang
2018-08-10 20:10 ` [PREVIEW] [PATCH v3 06/10] staging: erofs: fix compression mapping beyond EOF Gao Xiang
2018-08-11 14:42 ` Chao Yu
2018-08-12 7:49 ` [PREVIEW] [PATCH v4 " Gao Xiang
2018-08-10 20:10 ` [PREVIEW] [PATCH v3 07/10] staging: erofs: clean up z_erofs_map_blocks_iter Gao Xiang
2018-08-19 13:51 ` Chao Yu
2018-08-10 20:10 ` [PREVIEW] [PATCH v3 08/10] staging: erofs: complete error handing of z_erofs_map_blocks_iter Gao Xiang
2018-08-19 13:51 ` Chao Yu
2018-08-10 20:10 ` [PREVIEW] [PATCH v2 09/10] staging: erofs: fix a bug when appling cache strategy Gao Xiang
2018-08-19 13:52 ` Chao Yu
2018-08-10 20:10 ` [PREVIEW] [PATCH v2 10/10] staging: erofs: complete error handing of z_erofs_do_read_page Gao Xiang
2018-08-19 13:52 ` 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=fb551278-5e36-8a3c-e35b-6ffa2112cfd6@kernel.org \
--to=chao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox