From: Boaz Harrosh <bharrosh@panasas.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: LKP <fnstml-lkp@cn.fujitsu.com>,
Fengguang Wu <fengguang.wu@intel.com>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one_initcall()
Date: Mon, 25 Nov 2013 15:57:40 +0200 [thread overview]
Message-ID: <52935754.1070208@panasas.com> (raw)
In-Reply-To: <20131125132542.GX9991@yliu-dev.sh.intel.com>
On 11/25/2013 03:25 PM, Yuanhan Liu wrote:
>
> Hi Boaz,
>
> We are running an 0day kernel testing system. We will test all developers'
> tree we tracked in our system automatically. And obviously, linux-open-osd
> is in that list.
>
> This system can't tell whether a branch is experimental unless
> - You put one extra line of "Dont-Auto-Build" to the head commit log.
>
> - the branch name contains "experimental", say exofs_ioctl-experimental
>
> If both items aren't convenient to you, you can ask us to remove your
> tree from that list. Then you will never get report like this from us.
> However, you may lose a chance to find build, boot and performance bug
> automatically for you ;)
>
> --yliu
>
Ha OK very cool. I will remember to put -experimental on the branch name
this is fine I will do it ASAP.
Thanks so much. Do you have some web based info on the build system?
Do you have a place I can see test results and tests summery?
Cheers
Boaz
next prev parent reply other threads:[~2013-11-25 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 6:02 WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one_initcall() Yuanhan Liu
2013-11-25 10:43 ` Boaz Harrosh
2013-11-25 13:25 ` Yuanhan Liu
2013-11-25 13:57 ` Boaz Harrosh [this message]
2013-11-26 10:37 ` Yuanhan Liu
2013-11-26 10:54 ` Boaz Harrosh
2013-11-25 14:15 ` Richard Weinberger
2013-11-25 14:32 ` Boaz Harrosh
2013-11-25 14:43 ` Richard Weinberger
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=52935754.1070208@panasas.com \
--to=bharrosh@panasas.com \
--cc=fengguang.wu@intel.com \
--cc=fnstml-lkp@cn.fujitsu.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuanhan.liu@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox