From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
Subject: [PATCH for-4.20 0/7] erofs fixes for linux-4.20.y
Date: Mon, 25 Feb 2019 16:28:48 +0100 [thread overview]
Message-ID: <20190225152848.GE16015@kroah.com> (raw)
In-Reply-To: <20190222154637.22785-1-gaoxiang25@huawei.com>
On Fri, Feb 22, 2019@11:46:30PM +0800, Gao Xiang wrote:
> This series backports bugfixes already merged in linux upstream
> which we found these issues in our commercial products, which
> are serious and should be fixed immediately.
>
> Note that it also includes some xarray modification since
> upcoming patches heavily needs it, which can reduce more
> conflicts later.
>
> All patches have been tested again as a whole.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-02-25 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 15:46 [PATCH for-4.20 0/7] erofs fixes for linux-4.20.y Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 1/7] staging: erofs: remove the redundant d_rehash() for the root dentry Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 2/7] staging: erofs: atomic_cond_read_relaxed on ref-locked workgroup Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 3/7] staging: erofs: fix `erofs_workgroup_{try_to_freeze, unfreeze}' Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 4/7] staging: erofs: add a full barrier in erofs_workgroup_unfreeze Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 5/7] staging: erofs: {dir, inode, super}.c: rectify BUG_ONs Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 6/7] staging: erofs: unzip_{pagevec.h, vle.c}: " Gao Xiang
2019-02-22 15:46 ` [PATCH for-4.20 7/7] staging: erofs: unzip_vle_lz4.c, utils.c: " Gao Xiang
2019-02-25 15:28 ` Greg Kroah-Hartman [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=20190225152848.GE16015@kroah.com \
--to=gregkh@linuxfoundation.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