From: Lee Jones <lee.jones@linaro.org>
To: kbuild-all@lists.01.org
Subject: Re: Adding branches for testing
Date: Tue, 28 Jul 2020 10:25:24 +0100 [thread overview]
Message-ID: <20200728092524.GF2419169@dell> (raw)
In-Reply-To: <20200723080844.GM3533@dell>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
> > We have updated it: https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243
>
> Excellent. You are a star, thank you.
>
> I have added one more repo:
>
> https://github.com/intel/lkp-tests/pull/73
>
> Please see to it at your convenience.
Any idea why I am not receiving results for the following please?
https://github.com/intel/lkp-tests/blob/master/repo/linux/lee-linaro
As far as I'm aware, LKP should be testing all branches.
What am I missing? Did I do something wrong in the config?
--
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-28 9:25 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 [this message]
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
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=20200728092524.GF2419169@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.