From: Josip Rodin <joy@entuzijast.net>
To: xen-devel@lists.xensource.com
Subject: upstream merge status for 2.6.35, .36?
Date: Sat, 5 Jun 2010 00:39:29 +0200 [thread overview]
Message-ID: <20100604223929.GA8819@orion.carnet.hr> (raw)
Hi,
.35-rc1 has been tagged in mainline for a while now, and I noticed now that
two particular bug fixes from Ian's repo were added, so it looks like .35
will be bugfix only, too. If so, can someone update the wiki please?
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?
--
2. That which causes joy or happiness.
next reply other threads:[~2010-06-04 22:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 22:39 Josip Rodin [this message]
2010-06-05 0:20 ` upstream merge status for 2.6.35, .36? 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
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=20100604223929.GA8819@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).