linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>,
	linux-erofs@lists.ozlabs.org,
	Matthew Wilcox <willy@infradead.org>,
	David Howells <dhowells@redhat.com>, Chao Yu <yuchao0@huawei.com>,
	Miao Xie <miaoxie@huawei.com>,
	weidu.du@huawei.com
Subject: Re: [PATCH] Revert "staging: erofs: disable compiling temporarile"
Date: Tue, 28 Aug 2018 07:44:44 +0200	[thread overview]
Message-ID: <20180828054444.GA4453@kroah.com> (raw)
In-Reply-To: <1535427588-69630-1-git-send-email-gaoxiang25@huawei.com>

On Tue, Aug 28, 2018 at 11:39:48AM +0800, Gao Xiang wrote:
> This reverts commit 156c3df8d4db4e693c062978186f44079413d74d.
> 
> Since XArray and the new mount apis aren't merged in 4.19-rc1
> merge window, the BROKEN mark can be reverted directly without
> any problems.
> 
> Fixes: 156c3df8d4db ("staging: erofs: disable compiling temporarile")
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: David Howells <dhowells@redhat.com>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
> ---
> 
> Hi Greg,
> 
>  Could you please apply this patch to enable EROFS from 4.19-rc2, thanks...
> 
>  p.s. We would like to provide a more stable EROFS when linux-4.19 is out,
>       and there are also two patchsets (the one is already sent out by Chao
>       and me, the other is previewing in linux-erofs mailing list and it will
>       be sent out after gathering enough testdata and feedback from community
>       and carefully reviewed), could you also please consider applying these
>       two patchsets in the later 4.19-rc (both >2, or the first patchset
>       could be in rc2 in advance) if it is convenient to do so, or the next
>       4.20 is also ok...
> 
>  LINK: https://lore.kernel.org/lkml/20180821144937.20555-1-chao@kernel.org/
>        https://lore.kernel.org/lkml/1535076160-99466-1-git-send-email-gaoxiang25@huawei.com/

I applied those patch sets to my -next branch already, right?  So those
would be going into 4.20-rc1, it is time now for "bugfixes only" for
4.19-final.

So perhaps we should just leave it as "BROKEN" for now for 4.19 and add
this to my tree now and let people work on it for the next few months in
linux-next so that 4.20 has a solid base to start with?

thanks,

greg k-h

  reply	other threads:[~2018-08-28  5:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  3:39 [PATCH] Revert "staging: erofs: disable compiling temporarile" Gao Xiang
2018-08-28  5:44 ` Greg Kroah-Hartman [this message]
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

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=20180828054444.GA4453@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dhowells@redhat.com \
    --cc=gaoxiang25@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=weidu.du@huawei.com \
    --cc=willy@infradead.org \
    --cc=yuchao0@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).