All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Outstanding OSSTEST patch series
Date: Wed, 14 Jan 2015 09:46:10 +0000	[thread overview]
Message-ID: <1421228770.19103.177.camel@citrix.com> (raw)

Hi Ian,

I've got a few OSSTEST series out there which could use some review
attention, I'll list in decreasing order of priority (IMHO, YMMV, etc).

support for ARM32 arndale and cubietruck platforms

        v3 at <1416505070.26869.2.camel@citrix.com>
        
        Needed for new colo deployment since existing machine is not
        moving. New system is racked here in the meantime.
        
        About half acked, I think, but not many big consecutive lumps.
        
        I'm not sure if you were waiting for v4 with just the commit
        logs rewrapped or not. I have that locally if you want spamming
        a 4th time.
        
Implement for driving libvirt via virsh

        (I've just noticed that the title of this thread is nonsense...)
        
        v2 at <1417536141.29004.6.camel@citrix.com>
        
        No acks.
        
        Wei has (or will have?) some patches based on this (to add
        migration, which I punted on).
        
add distro domU testing flight

        v3 at <1417438571.29138.22.camel@citrix.com>
        
        A couple of acks.
        
        As well as enabling testing of Debian as a guest using D-I as a
        standalone flight (suitable for other distros to be added too),
        also enables pygrub and pvgrub (1 only for now) testing for
        regular flights (probably more valuable in the grand scheme of
        things).
        
        It also lays the ground work for testing non-LVM backed guests
        (qcow2, vhd and raw file for now), I have follow on patches
        which I haven't posted yet, I'll include it in v4 but it would
        be best to flush some of the queue before adding those to the
        mix I think.

I think the last postings are all still relevant to look at, but I can
resend if you prefer like (beware that they are 15, 18 & 19 patches
respectively, with the 19 having more added for v4...)

Ian.

             reply	other threads:[~2015-01-14  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  9:46 Ian Campbell [this message]
2015-01-14 10:19 ` Outstanding OSSTEST patch series Wei Liu
2015-01-14 10:33   ` Ian Campbell
2015-01-14 10:45     ` Wei Liu
2015-01-14 17:05       ` Ian Jackson
2015-01-20 14:07     ` Dario Faggioli
2015-01-22 15:50       ` Ian Campbell
2015-01-20 18:16 ` Ian Jackson

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=1421228770.19103.177.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.