From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: Adding Thermal SoC tree into 0-Day testing
Date: Fri, 28 Oct 2016 22:43:25 +0800 [thread overview]
Message-ID: <20161028144325.GA15479@intel.com> (raw)
In-Reply-To: <CAC-25o-ydeewuWQYrSQs0FHtrTTqYbdLoUSn5uHZq8U18PwEFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]
On Fri, Oct 28, 2016 at 07:26:50AM -0700, edubezval(a)gmail.com wrote:
> Philip,
>
> On Fri, Oct 28, 2016 at 1:29 AM, Philip Li <philip.li@intel.com> wrote:
> > On Thu, Oct 27, 2016 at 10:29:23PM -0700, edubezval(a)gmail.com wrote:
> >> Hello 0-Day team,
> >>
> >> I would like to ask you if you could add my tree to your testing service:
> >>
> >> tree: https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/
> >> branches: linus, next, for-kernelci
> >>
> >> Would you also send reports on changes in the branches?
> >
> > sure, np, to confirm, currently we have below repo monitored, and this one is a different one, right?
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git
> >
>
> Cool, I am still getting familiar with 0-Day. I did not realize you
> guys monitor per repo, not per branch. Great!
thanks, and do you still need us to add the new repo https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/?
>
> I have a couple of questions.
>
> How do I access build reports and test reports? Is the mailing list
> the right place, or do you also have a place with your past / current
> results?
Currently you will receive report when there's any regression detected. I will later add build success notification to you as well.
The place to check is https://lists.01.org/pipermail/kbuild-all/, and https://lists.01.org/pipermail/lkp/ for all reports.
>
> I saw that you do a simple read of thermal zone temperatures, and
> cooling devices actions, which is great for me. If I want to extend
> thermal tests, how do I do it?
>
> And finally, which archs and devices do you test?
For thermal related questions, let me consult more members and back to you later.
>
> BR,
>
> >>
> >> BR,
> >>
> >> --
> >> Eduardo Bezerra Valentin
> >> _______________________________________________
> >> LKP mailing list
> >> LKP(a)lists.01.org
> >> https://lists.01.org/mailman/listinfo/lkp
>
>
>
> --
> Eduardo Bezerra Valentin
next prev parent reply other threads:[~2016-10-28 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 5:29 Adding Thermal SoC tree into 0-Day testing edubezval
2016-10-28 8:29 ` Philip Li
2016-10-28 14:26 ` edubezval
2016-10-28 14:43 ` Philip Li [this message]
2016-10-28 15:19 ` edubezval
2016-10-31 5:01 ` Philip Li
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=20161028144325.GA15479@intel.com \
--to=philip.li@intel.com \
--cc=lkp@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.