xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Josip Rodin <joy@entuzijast.net>
To: xen-devel@lists.xensource.com
Subject: Re: upstream merge status for 2.6.35, .36?
Date: Mon, 7 Jun 2010 10:32:01 +0200	[thread overview]
Message-ID: <20100607083201.GA16443@orion.carnet.hr> (raw)
In-Reply-To: <20100607074811.GV17817@reaktio.net>

On Mon, Jun 07, 2010 at 10:48:11AM +0300, Pasi Kärkkäinen wrote:
> On Fri, Jun 04, 2010 at 05:20:06PM -0700, Jeremy Fitzhardinge wrote:
> > On 06/04/2010 03:39 PM, Josip Rodin wrote:
> > > What about the future? I saw Konrad's applied his swiotlb tree with the
> > > right acks for inclusion into linux-next, so that looks like it's planned
> > > to be ready to go in when the .36 merge window opens, right?
> > 
> > Yes, and I'm hoping we can get pcifront and pvhvm lined up for .36; with
> > those in place, its a short jump to full dom0 functionality (which, no
> > promises, might also get into .36 on their tails).
> 
> swiotlb seems to be in linux-next now.. Congratulations!

Yes, http://lkml.org/lkml/2010/6/5/71

Now that looks exceedingly smooth, but if you look at the date on
http://lkml.org/lkml/2009/5/11/223 ... on the bright side, the new swiotlb
branch is both peer-reviewed and user-tested in xen/stable-2.6.32.x AFAICT,
so the end-result should be bulletproof (as much as it can be :).

-- 
     2. That which causes joy or happiness.

  reply	other threads:[~2010-06-07  8:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 22:39 upstream merge status for 2.6.35, .36? Josip Rodin
2010-06-05  0:20 ` Jeremy Fitzhardinge
2010-06-05 12:51   ` Josip Rodin
2010-06-06  0:36     ` Jeremy Fitzhardinge
2010-06-06  7:36       ` upstream merge status for 2.6.35, .36? PV on HVM Xen Boris Derzhavets
2010-06-07  7:48   ` upstream merge status for 2.6.35, .36? Pasi Kärkkäinen
2010-06-07  8:32     ` Josip Rodin [this message]
2010-06-07 14:57       ` Konrad Rzeszutek Wilk
2010-06-07 15:24         ` Sander Eikelenboom
2010-06-07 16:15           ` Konrad Rzeszutek Wilk
2010-06-07 17:12         ` Josip Rodin
2010-06-07 18:07           ` Konrad Rzeszutek Wilk
2010-06-07 18:33           ` Jeremy Fitzhardinge
2010-06-08  7:57             ` Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0 Boris Derzhavets
2010-06-08 17:29               ` Jeremy Fitzhardinge
2010-08-04 19:44         ` upstream merge status for 2.6.35, .36? Josip Rodin
2010-08-04 20:11           ` Konrad Rzeszutek Wilk
2010-08-04 21:09             ` Łukasz Oleś
2010-08-04 21:38             ` Josip Rodin
2010-08-05 15:22               ` Konrad Rzeszutek Wilk
2010-08-07 22:50                 ` Josip Rodin
2010-08-08  1:02                   ` Jeremy Fitzhardinge
2010-06-07 16:47     ` Jeremy Fitzhardinge

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=20100607083201.GA16443@orion.carnet.hr \
    --to=joy@entuzijast.net \
    --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 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).