From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: Please add git tree
Date: Fri, 11 Mar 2016 16:08:08 +0800 [thread overview]
Message-ID: <20160311080808.GA18000@intel.com> (raw)
In-Reply-To: <20160310154048.GH2464@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Thu, Mar 10, 2016 at 10:40:48AM -0500, Matthew Wilcox wrote:
> On Mon, Mar 07, 2016 at 01:01:53PM +0800, Philip Li wrote:
> > On Sun, Mar 06, 2016 at 10:06:42PM -0500, Matthew Wilcox wrote:
> > >
> > > Please add
> > >
> > > git://git.infradead.org/users/willy/linux-dax.git
> >
> > sure, this is added, and build status will be notified.
>
> I found some build errors in this tree. Is it possible that 0day is
> failing to test some x86-32 configs?
do you mean you receive 0day report, and it shows failure?
>
> Combinations of Kconfig symbols that I want to see tested:
>
> 64BIT
> X86_PAE
> HIGHMEM
> HIGHMEM4G
> HIGHMEM64G
> NOHIGHMEM
> TRANSPARENT_HUGEPAGE
> DAX
currently 0day will do a lot randconfig besides some standard one like allyes, allmodule.
it will have possibility to cover the combination here.
>
> (some of these interact with each other in fun ways, so it's fewer than
> 2^8 different configs)
>
> Is there a way to see what configs were tested against a particular
> branch? I'd also like to know whether pSeries was tested.
>
usually for a build notification mail, 0day will list all the configs tested again which commit/branch.
and what is pSeries here?
thanks
next prev parent reply other threads:[~2016-03-11 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 3:06 Please add git tree Matthew Wilcox
2016-03-07 5:01 ` Philip Li
2016-03-10 15:40 ` Matthew Wilcox
2016-03-11 8:08 ` Philip Li [this message]
2016-03-11 8:50 ` Fengguang Wu
2016-03-11 8:54 ` Fengguang Wu
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=20160311080808.GA18000@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.