mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Howells <dhowells@redhat.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Gao Xiang <gaoxiang25@huawei.com>, <devel@driverdev.osuosl.org>,
	Miao Xie <miaoxie@huawei.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>, <weidu.du@huawei.com>,
	<linux-erofs@lists.ozlabs.org>
Subject: Re: [PATCH] Revert "staging: erofs: disable compiling temporarile"
Date: Wed, 12 Sep 2018 16:33:53 +0800	[thread overview]
Message-ID: <bdb3e07b-b769-34a4-28c9-630131db2c55@huawei.com> (raw)
In-Reply-To: <20180912173404.288ea2e5@canb.auug.org.au>

Hi Stephen,

On 2018/9/12 15:34, Stephen Rothwell wrote:
> Hi Chao,
> 
> On Wed, 12 Sep 2018 15:19:16 +0800 Chao Yu <yuchao0@huawei.com> wrote:
>>
>> To make sure, did -next tree enable erofs compiling now?
> 
> Yes, from yesterday.

Great, thanks for your help. :)

> 
>> Xiang has made two patches to fix integration issue with other vfs changes,
>> and Greg and David have already picked them in their tree.
>>
>> staging: erofs: rename superblock flags (MS_xyz -> SB_xyz)
>> staging: erofs: update .mount and .remount_sb
> 
> I noticed, thanks.
> 


      reply	other threads:[~2018-09-12  8:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  3:39 Gao Xiang
2018-08-28  5:44 ` Greg Kroah-Hartman
2018-08-28  6:28   ` Gao Xiang
2018-08-28  8:56     ` Chao Yu
2018-08-28 13:05       ` Greg Kroah-Hartman
2018-08-28 13:10         ` Gao Xiang
2018-08-28 14:13         ` Chao Yu
2018-08-28 23:44           ` Stephen Rothwell
2018-08-29  1:37             ` Gao Xiang
2018-09-05 23:25             ` Stephen Rothwell
2018-09-06  2:06               ` Gao Xiang
2018-09-12  7:19               ` Chao Yu
2018-09-12  7:34                 ` Stephen Rothwell
2018-09-12  8:33                   ` Chao Yu [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=bdb3e07b-b769-34a4-28c9-630131db2c55@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dhowells@redhat.com \
    --cc=gaoxiang25@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=weidu.du@huawei.com \
    --cc=willy@infradead.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
all inboxes | Powered by JetHome®