From: Lee Jones <lee.jones@linaro.org>
To: kbuild-all@lists.01.org
Subject: Re: Adding branches for testing
Date: Thu, 23 Jul 2020 09:09:25 +0100 [thread overview]
Message-ID: <20200723080925.GN3533@dell> (raw)
In-Reply-To: <40833ab8-8a33-b452-ae61-6574bbaaa992@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3139 bytes --]
On Thu, 23 Jul 2020, Rong Chen wrote:
>
>
> On 7/23/20 3:27 PM, Lee Jones wrote:
> > On Thu, 23 Jul 2020, Rong Chen wrote:
> >
> > >
> > > On 7/23/20 2:32 PM, Lee Jones wrote:
> > > > On Wed, 22 Jul 2020, Nathan Chancellor wrote:
> > > >
> > > > > Hi Lee,
> > > > >
> > > > > On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
> > > > > > Good evening,
> > > > > >
> > > > > > Is it possible to obtain build-test results for successful builds?
> > > > > >
> > > > > > If so, what is the process for adding branches to your system?
> > > > > >
> > > > > > Thanks in advance.
> > > > > >
> > > > > > Kind regards,
> > > > > > Lee
> > > > > >
> > > > > I filed a pull request against their repository and I get email
> > > > > notifications whenever I push to a new branch on my repository:
> > > > >
> > > > > https://github.com/intel/lkp-tests/pull/64
> > > > Of course it's on GitHub! :)
> > > >
> > > > There was me thinking it was secret source.
> > > >
> > > > > Looks like there are a lot of trees to look over in case you want to
> > > > > customize it in some way, I am not sure of any documentation over it
> > > > > though:
> > > > Docs:
> > > >
> > > > https://github.com/intel/lkp-tests
> > > > https://github.com/intel/lkp-tests/wiki
> > > >
> > > > > https://github.com/intel/lkp-tests/tree/master/repo/linux
> > > > You've been a great help Nathan. Thank you!
> > > >
> > > Hi Lee, Nathan,
> > >
> > > We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
> > > and there is a introduce document for these items:
> > > https://github.com/intel/lkp-tests/wiki/Repo-Spec
> > Would you be kind enough to expand on a couple of points for me
> > please? The Repo-Spec seems to be lacking in a couple of areas.
> >
> > What are 'integration_testing_branches'? Will lkp-tests only operate
> > on those branches and exclude all others (except those mentioned in
> > 'whitelist_branch' of course).
>
> Hi Lee,
>
> the branches of integration_testing_branches are from linux-next tree,
> 'integration_testing_branches' means 0day will try to apply lkml patches to
> these branches to test.
>
> $ git show linux-next/master:Next/Trees | grep lee/mfd
> mfd-fixes git
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-fixes
> mfd git
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-next
>
> >
> > What are 'subsystems'? If the MFD case, these do not appears to be
> > directories. Do they pertain to something else, regex for instance?
>
> 'subsystems' is generated from linus/master:MAINTAINERS, 0day use it to compare with the patch subject from lkml,
> and sort the branches that the patch may want to be applied to.
Okay, that makes sense.
Thank you for taking the time to explain.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-07-23 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200723035548.GA363815@ubuntu-n2-xlarge-x86>
2020-07-23 6:32 ` Adding branches for testing Lee Jones
2020-07-23 6:38 ` Rong Chen
2020-07-23 6:46 ` Lee Jones
2020-07-23 7:58 ` Rong Chen
2020-07-23 8:08 ` Lee Jones
2020-07-28 9:25 ` Lee Jones
2020-07-29 9:09 ` Rong Chen
2020-07-29 10:13 ` Lee Jones
2020-07-30 1:21 ` Rong Chen
2020-07-23 7:27 ` Lee Jones
2020-07-23 7:57 ` Rong Chen
2020-07-23 8:09 ` Lee Jones [this message]
2020-07-17 21:22 [ljones-mfd:for-mfd-next 56/66] drivers/mfd/mfd-core.c:216:11: error: implicit declaration of function 'mfd_match_of_node_to_dev' kernel test robot
2020-07-22 18:03 ` Adding branches for testing Lee Jones
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=20200723080925.GN3533@dell \
--to=lee.jones@linaro.org \
--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.