From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5690077016489932035==" MIME-Version: 1.0 From: Gao Xiang To: kbuild-all@lists.01.org Subject: Re: erofs tree integration testing.... Date: Fri, 11 Oct 2019 13:47:15 +0800 Message-ID: <20191011054714.GA170263@architecture4> In-Reply-To: List-Id: --===============5690077016489932035== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Rong, On Fri, Oct 11, 2019 at 12:44:21PM +0800, Rong Chen wrote: > Hi Gao Xiang, > = > On 10/11/19 8:46 AM, Philip Li wrote: > > On Thu, Oct 10, 2019 at 05:18:50PM +0800, Gao Xiang wrote: > > > Hi Philip, > > > = > > > On Mon, Jul 29, 2019 at 11:25:04PM +0800, Philip Li wrote: > > > > On Mon, Jul 29, 2019 at 05:09:36PM +0800, Gao Xiang wrote: > > > [] > > > = > > > > > > > It is due to that I moved EROFS_SUPER_MAGIC_V1 from > > > > > > > linux/fs/erofs/erofs_fs.h to > > > > > > > include/uapi/linux/magic.h and I fixed it just now... > > > > > > > = > > > > > > > Could you help re-test again? > > > > > > thanks, you can submit patch to your repo, we will automaticall= y fetch > > > > > > it to test. > > > > > Thank you, it will be of great help if testing my linux.git :) > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git/ > > > > sure, this is already in our monitoring > > > > = > > > > > (BTW. could you kindly send test report to my community email xia= ng(a)kernel.org as well?) > > > > ok, i had added it in cc list. > > > > = > > > > you can check https://github.com/intel/lkp-tests/blob/master/repo/l= inux/xiang-linux, and > > > > if you need update it in future, feel free to send PR. > > > Is there some chance to do integration testing for kernel erofs tree? > > > git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git > > sure, we will add this soon. > > = > > Hi Rong, can you help on the requests in this mail? > I have added it. Thanks for your suggestion. Thanks for quick deployment. It will help a lot! > = > > = > > > The following branch could be used for integration testing: > > > -b dev (for -next) > > > -b fixes (fixes only for this round) > > > = > > > and I think another git_am_branch could be used for the build testing= ... > > > -b dev-test (I will create this branch hours later)... > > got it > > = > > > maybe also mail-cc for the results of above branches: > > > linux-erofs(a)lists.ozlabs.org > > > = > > > success emails for my korg email: xiang(a)kernel.org > > > = > > > (BTW, my personal repo recently didn't receive some BUILD SUCCESS kbu= ild email > > > git://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git > > > , is there something wrong?....) > > Hi Rong, kindly check. > We won't test the branches named with "experimental" by default, could you > use other branch names, > or tell us the naming rule of branches that need to be tested? Oh, I see. I will change to another names, thanks for telling me about that= .. [thumb] Thanks, Gao Xiang > = > Best Regards, > Rong Chen > = > > = > > > Thanks, > > > Gao Xiang > > > = >=20 --===============5690077016489932035==--