From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael Brade <brade@kde.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: PATCH: Jeremy's linux 2.6.33-pvops: wrong gntdev
Date: Mon, 02 Aug 2010 08:26:30 -0700 [thread overview]
Message-ID: <4C56E3A6.7010809@goop.org> (raw)
In-Reply-To: <201008012127.17188.brade@kde.org>
On 08/01/2010 12:27 PM, Michael Brade wrote:
> Hi,
>
> I have compiled Xen and Jeremy's linux-2.6-pvops.git kernel, branch
> "xen/stable-2.6.33.x". This branch uses the wrong gntdev name though, Xen
> says:
Sorry, .33.x is very "stable" in the sense that I haven't really been
updating it. As Pasi says, 32.x is where the action is at the moment.
Once .35 comes out, I plan to make that the new base for development
(though .32 will be maintained for the long term).
J
next prev parent reply other threads:[~2010-08-02 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 19:27 PATCH: Jeremy's linux 2.6.33-pvops: wrong gntdev Michael Brade
2010-08-02 13:41 ` Pasi Kärkkäinen
2010-08-02 15:26 ` Jeremy Fitzhardinge [this message]
2010-08-04 17:30 ` Michael Brade
2010-08-04 17:54 ` Jeremy Fitzhardinge
2010-08-04 18:43 ` Michael Brade
2010-08-04 19:21 ` 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=4C56E3A6.7010809@goop.org \
--to=jeremy@goop.org \
--cc=brade@kde.org \
--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).