All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 2/2] f2fs-tools: relocate chksum_offset for large_nat_bitmap feature
Date: Sat, 6 Jul 2019 09:39:28 +0800	[thread overview]
Message-ID: <990f0732-9c6b-1525-32bd-6b4c16f3befe@kernel.org> (raw)
In-Reply-To: <20190705183152.GB57189@jaegeuk-macbookpro.roam.corp.google.com>

On 2019-7-6 2:31, Jaegeuk Kim wrote:
> Hi guys,
> 
> On 07/01, Chao Yu wrote:
>> Ping, Jaegeuk,
>>
>> On 2019/7/1 14:23, Ju Hyung Park wrote:
>>> One more bump.
>>>
>>> afaik, there's only about a week left.
>>>
>>> Thanks.
>>>
>>> On Thu, Jun 27, 2019 at 7:20 PM Chao Yu <yuchao0@huawei.com> wrote:
>>>>
>>>> Hi Ju Hyung,
>>>>
>>>> Thanks for the reminding.
>>>>
>>>> Jaegeuk, I can send the kernel patch after you tag a new version on fsck.
> 
> You can use 1.13.0.

Jaegeuk, thanks, let me use that. ;)

Thanks,

> 
> Thanks,
> 
>>>>
>>>> Thanks,
>>>>
>>>> On 2019/6/27 17:12, Ju Hyung Park wrote:
>>>>> Hi Jaegeuk and Chao.
>>>>>
>>>>> A little bump here.
>>>>>
>>>>> We still need to tag a new version of fsck and update f2fs kernel code
>>>>> to tell which version users should use as we discussed earlier.
>>>>> -rc is closing soon, so I felt I needed to remind you.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Tue, Jun 4, 2019 at 10:48 AM Chao Yu <yuchao0@huawei.com> wrote:
>>>>>>
>>>>>> On 2019/6/4 4:27, Jaegeuk Kim wrote:
>>>>>>> On 06/04, Ju Hyung Park wrote:
>>>>>>>> Hi Jaegeuk and Chao,
>>>>>>>>
>>>>>>>> A little update I thought I might share.
>>>>>>>>
>>>>>>>> Just went through migrating my laptop to another SSD and I've setup
>>>>>>>> f2fs from the beginning with mkfs -i from the master branch.
>>>>>>>> No issue as of yet and the kernel is working fine as expected :)
>>>>>>>
>>>>>>> Cool, thanks for your test. :)
>>>>>>
>>>>>> Great, thanks for the continuous test and report. :)
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Linux-f2fs-devel mailing list
>>>>>>>> Linux-f2fs-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Linux-f2fs-devel mailing list
>>>>>>> Linux-f2fs-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>>>>>>> .
>>>>>>>
>>>>> .
>>>>>
>>> .
>>>
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2019-07-06  1:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  9:33 [PATCH v3 1/2] f2fs-tools: allow unfixed f2fs_checkpoint.checksum_offset Chao Yu
2019-05-14  9:33 ` [PATCH v3 2/2] f2fs-tools: relocate chksum_offset for large_nat_bitmap feature Chao Yu
     [not found]   ` <CAD14+f2ckNUv9n-Zb9UL_ojX8=24tYBhT-SsrcpVNogqee2tkA@mail.gmail.com>
2019-05-14  9:43     ` Chao Yu
     [not found]       ` <CAD14+f3NHosrL=5UOBSMbFxQ91x-AuWOj_w=JYkJSnmfDgTkvA@mail.gmail.com>
2019-05-15  4:50         ` Ju Hyung Park
2019-05-15  9:23           ` Chao Yu
2019-05-18 20:09             ` Ju Hyung Park
2019-05-19  5:09               ` Chao Yu
2019-05-19  9:19                 ` Ju Hyung Park
2019-05-19 15:09                   ` Chao Yu
2019-06-03 15:23                     ` Ju Hyung Park
2019-06-03 20:27                       ` Jaegeuk Kim
2019-06-04  1:48                         ` Chao Yu
2019-06-27  9:12                           ` [f2fs-dev] " Ju Hyung Park
2019-06-27 10:20                             ` Chao Yu
2019-07-01  6:23                               ` Ju Hyung Park
2019-07-01  9:43                                 ` Chao Yu
2019-07-05 18:31                                   ` Jaegeuk Kim
2019-07-06  1:39                                     ` 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=990f0732-9c6b-1525-32bd-6b4c16f3befe@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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 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.