From: sashal@kernel.org (Sasha Levin)
Subject: [PREVIEW] [PATCH] staging: erofs: fix mis-acted TAIL merging behavior
Date: Wed, 23 Jan 2019 22:57:49 +0000 [thread overview]
Message-ID: <20190123225749.DDDF6218A4@mail.kernel.org> (raw)
In-Reply-To: <20190122124530.5621-1-gaoxiang25@huawei.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 3883a79abd02 staging: erofs: introduce VLE decompression support.
The bot has tested the following trees: v4.20.3, v4.19.16.
v4.20.3: Build OK!
v4.19.16: Failed to apply! Possible dependencies:
ab47dd2b0819 ("staging: erofs: cleanup z_erofs_vle_work_{lookup, register}")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-23 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 12:45 [PREVIEW] [PATCH] staging: erofs: fix mis-acted TAIL merging behavior Gao Xiang
2019-01-22 12:45 ` Gao Xiang
2019-01-23 22:57 ` Sasha Levin [this message]
2019-01-24 2:58 ` Gao Xiang
2019-01-24 2:58 ` Gao Xiang
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=20190123225749.DDDF6218A4@mail.kernel.org \
--to=sashal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.