All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Iain Kay <spam@iainkay.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Looking for xen-blkback patch for 2.6.39 kernel
Date: Fri, 3 Jun 2011 11:46:57 -0400	[thread overview]
Message-ID: <20110603154657.GB12708@dumpdata.com> (raw)
In-Reply-To: <4AA8FE05-2C28-4A2B-81C1-D434C41AAB86@iainkay.com>

On Fri, Jun 03, 2011 at 03:12:24PM +0100, Iain Kay wrote:
> > Btw did you realize xen-blkback is already merged to upstream Linux v3.0-rc1 ?
> > 
> > -- Pasi
> 
> I was not aware no. I hadn't really considered it to be honest. My thoughts where that 2.6.39 is here and 'stable' whereas the 3.0 is an entire new major revision and is likely to introduce a less stable experience.

If you just want the patchset of xen-blkback against 2.6.39, go get the this branch

stable/xen-blkback-v3.3

from: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git

thought you will also need to extra patches on top, which are in in stable/backend.base.v3
to compile.

Or you can just get the 2.6.39 stable tree that has those patches and some more from

stable/2.6.39.x

  parent reply	other threads:[~2011-06-03 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 14:12 Looking for xen-blkback patch for 2.6.39 kernel Iain Kay
2011-06-03 14:22 ` Ian Campbell
2011-06-03 15:46 ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-03 17:50 Iain Kay
2011-06-03 19:46 ` Dan Magenheimer
2011-06-03 20:19   ` Iain Kay
2011-06-03 14:11 Iain Kay
2011-06-03 14:09 Iain Kay
2011-06-03 10:41 Iain Kay
2011-06-03 10:48 ` Ian Campbell
2011-06-03 11:05   ` Iain Kay
2011-06-03 11:25     ` Pasi Kärkkäinen
2011-06-03 12:02     ` Ian Campbell

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=20110603154657.GB12708@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=spam@iainkay.com \
    --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.