Hi Stephen,
On 2018/9/12 15:34, Stephen Rothwell wrote:
> Hi Chao,
>
> On Wed, 12 Sep 2018 15:19:16 +0800 Chao Yu 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
Hi Chao,
On Wed, 12 Sep 2018 15:19:16 +0800 Chao Yu wrote:
>
> To make sure, did -next tree enable erofs compiling now?
Yes, from yesterday.
> 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:
Hi Stephen,
To make sure, did -next tree enable erofs compiling now?
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
Hi David, Al,
On 2018/9/6 7:25, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 29 Aug 2018 09:44:03 +1000 Stephen Rothwell
> wrote:
>>
>> On Tue, 28 Aug 2018 22:13:02 +0800 Chao Yu wrote:
>>>
>>> On 2018/8/28 21:05, Greg Kroah-Hartman wrote:
On Tue, Aug 28, 2018 at 04:56:43PM +0800,
Hi all,
On Wed, 29 Aug 2018 09:44:03 +1000 Stephen Rothwell
wrote:
>
> On Tue, 28 Aug 2018 22:13:02 +0800 Chao Yu wrote:
> >
> > On 2018/8/28 21:05, Greg Kroah-Hartman wrote:
> > > On Tue, Aug 28, 2018 at 04:56:43PM +0800, Chao Yu wrote:
> > >>
> > >> On 2018/8/28 14:28, Gao Xiang wrote:
On 2018/8/29 7:44, Stephen Rothwell wrote:
> Unfortunately, those vfs changes are still in the vfs tree in
> linux-next and cause a build failure in the erofs code. I have
> disabled the build of erofs again for today.
feel a bit loss after hear that... :'(
>
> Dave, Al, it would be good if
Hi all,
On Tue, 28 Aug 2018 22:13:02 +0800 Chao Yu wrote:
>
> On 2018/8/28 21:05, Greg Kroah-Hartman wrote:
> > On Tue, Aug 28, 2018 at 04:56:43PM +0800, Chao Yu wrote:
> >> Hi Greg,
> >>
> >> On 2018/8/28 14:28, Gao Xiang wrote:
> >>> Hi Greg,
> >>>
> >>> On 2018/8/28 13:44, Greg
On 2018/8/28 21:05, Greg Kroah-Hartman wrote:
> On Tue, Aug 28, 2018 at 04:56:43PM +0800, Chao Yu wrote:
>> Hi Greg,
>>
>> On 2018/8/28 14:28, Gao Xiang wrote:
>>> Hi Greg,
>>>
>>> On 2018/8/28 13:44, Greg Kroah-Hartman wrote:
On Tue, Aug 28, 2018 at 11:39:48AM +0800, Gao Xiang wrote:
>
Hi Greg,
On 2018/8/28 21:05, Greg Kroah-Hartman wrote:
> On Tue, Aug 28, 2018 at 04:56:43PM +0800, Chao Yu wrote:
>> Hi Greg,
>>
>> On 2018/8/28 14:28, Gao Xiang wrote:
>>> Hi Greg,
>>>
>>> On 2018/8/28 13:44, Greg Kroah-Hartman wrote:
On Tue, Aug 28, 2018 at 11:39:48AM +0800, Gao Xiang
On Tue, Aug 28, 2018 at 04:56:43PM +0800, Chao Yu wrote:
> Hi Greg,
>
> On 2018/8/28 14:28, Gao Xiang wrote:
> > Hi Greg,
> >
> > On 2018/8/28 13:44, Greg Kroah-Hartman wrote:
> >> On Tue, Aug 28, 2018 at 11:39:48AM +0800, Gao Xiang wrote:
> >>> This reverts commit
Hi Greg,
On 2018/8/28 14:28, Gao Xiang wrote:
> Hi Greg,
>
> On 2018/8/28 13:44, Greg Kroah-Hartman wrote:
>> 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
Hi Greg,
On 2018/8/28 13:44, Greg Kroah-Hartman wrote:
> 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
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
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
Cc:
14 matches
Mail list logo
