From: Fengguang Wu <fengguang.wu@intel.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [do_xor_speed] WARNING: CPU: 0 PID: 1 at init/main.c:708 do_one_initcall()
Date: Mon, 31 Mar 2014 19:18:49 +0800 [thread overview]
Message-ID: <20140331111849.GA12489@localhost> (raw)
In-Reply-To: <53394A11.6060204@panasas.com>
On Mon, Mar 31, 2014 at 01:57:21PM +0300, Boaz Harrosh wrote:
> On 03/31/2014 11:13 AM, Fengguang Wu wrote:
> > On Mon, Mar 31, 2014 at 10:08:51AM +0300, Boaz Harrosh wrote:
> >> Sorry about that I forgot about the experimental rule, fixed now.
> >>
> >> Is there a way for a white list. With -experimental I need to say
> >> every branch I do not want included is there a way to say only
> >> the branches I do want included?
> >
> > Yes, sure. You can tell me a list of branch patterns that is suitable
> > for testing and I can blacklist everything else in your tree.
> >
> > Thanks,
> > Fengguang
> >
>
> Thanks Wu, I hate to be trouble. Am I the only one who has this
> problem ? Its that I use this git tree also as a public development
> tree, when need of collaboration.
You are not the only one that needs the manual blacklist/whitelist -
that's why we already have this mechanism. :)
> For now it is good, I'll try to remember when I push new branches
Or better, we are not feeling bothered at all when hit bugs in your
and others' WIP trees - it's an achievement to be able to catch more
bugs, and our test system is designed to do the job efficiently. :)
Thanks,
Fengguang
prev parent reply other threads:[~2014-03-31 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 0:38 [do_xor_speed] WARNING: CPU: 0 PID: 1 at init/main.c:708 do_one_initcall() Fengguang Wu
2014-03-31 7:08 ` Boaz Harrosh
2014-03-31 8:13 ` Fengguang Wu
2014-03-31 10:57 ` Boaz Harrosh
2014-03-31 11:18 ` Fengguang Wu [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=20140331111849.GA12489@localhost \
--to=fengguang.wu@intel.com \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).