All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <gaoxiang25@huawei.com>
To: kbuild-all@lists.01.org
Subject: Re: erofs tree integration testing....
Date: Fri, 11 Oct 2019 13:47:15 +0800	[thread overview]
Message-ID: <20191011054714.GA170263@architecture4> (raw)
In-Reply-To: <a2b20bea-d39a-a2ae-4914-9cc6383745a7@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]

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 automatically 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 xiang(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/linux/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 kbuild 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
> > > 
> 

      reply	other threads:[~2019-10-11  5:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190729152504.GG22821@intel.com>
2019-10-10  9:18 ` erofs tree integration testing Gao Xiang
2019-10-11  0:43   ` Philip Li
2019-10-11  4:46     ` Rong Chen
2019-10-11  5:47       ` Gao Xiang [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=20191011054714.GA170263@architecture4 \
    --to=gaoxiang25@huawei.com \
    --cc=kbuild-all@lists.01.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 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.