All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [linux-mingo-tip-master test] 17105: regressions - FAIL
Date: Tue, 5 Mar 2013 13:16:04 -0500	[thread overview]
Message-ID: <20130305181603.GB24062@phenom.dumpdata.com> (raw)
In-Reply-To: <1664322890.20130305173750@eikelenboom.it>

On Tue, Mar 05, 2013 at 05:37:50PM +0100, Sander Eikelenboom wrote:
> 
> Tuesday, March 5, 2013, 5:29:22 PM, you wrote:
> 
> > Sander Eikelenboom writes ("Re: [Xen-devel] [linux-mingo-tip-master test] 17105: regressions - FAIL"):
> >> Tuesday, March 5, 2013, 5:13:10 PM, you wrote:
> >> > I poked hpa about it and he mentioned that Ingo sporadically updates
> >> > his tree.  So going to poke him in a week since v3.9-rc1 just
> >> > came out.
> >> 
> >> Would it be an idea to setup a branch (in konrad's tree) that follows tip-master, but allows konrad to apply patches that are "under way" (accepted but not yet applied)  and are important (needed to boot etc ?) and test that one instead ?
> 
> > That would be simple from my pov.  I don't have an opinion about it.
> 
> It's as always a tradeoff, an extra burden for Konrad, but less wastage of test resources.
> Could be something like a "linux-next" but then only for Xen-patches applied on top of branch tracking perhaps the most important tree (x86).
> Testing linux-next it self could probably hang on to many non Xen related problems.

Actually, linux-next could be a good option too. It is suppose to be the next
thing going to Linus so hopefully working.

Ian, would it be possible to set this up?
> 
> > Ian.
> 
> 

      reply	other threads:[~2013-03-05 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 12:51 [linux-mingo-tip-master test] 17105: regressions - FAIL xen.org
2013-03-05 16:13 ` Konrad Rzeszutek Wilk
2013-03-05 16:26   ` Sander Eikelenboom
2013-03-05 16:29     ` Ian Jackson
2013-03-05 16:37       ` Sander Eikelenboom
2013-03-05 18:16         ` Konrad Rzeszutek Wilk [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=20130305181603.GB24062@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xensource.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 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.