All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] (xen) stable/blkfront for 2.6.40
Date: Thu, 12 May 2011 09:27:15 -0400	[thread overview]
Message-ID: <20110512132715.GC11649@dumpdata.com> (raw)
In-Reply-To: <4DCACD25.6060107@kernel.dk>

On Wed, May 11, 2011 at 07:53:41PM +0200, Jens Axboe wrote:
> On 2011-05-10 19:11, Konrad Rzeszutek Wilk wrote:
> > Hey Jens,
> > 
> > Please pull:
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/blkfront
> > 
> > which has changes since git commit 8e10cd74342c7f5ce259cceca36f6eba084f5d58
> > Linus Torvalds (1):
> >     Linux 2.6.39-rc5
> > 
> > The git commit includes a bug-fix, and a set of patches to allow the blkfront
> > driver to use 'feature-flush-cache' feature. The 'flush-cache' is basically
> > the equivalent of the new REQ_FLUSH command (the old 'feature-barrier' is
> > still present in the driver in case the backend supports that).
> > 
> > If you prefer for me to ask Linus to pull this git tree since it includes
> > a patch to the include/xen/interface/.. directory - I can do that as long as
> > you are OK with that.
> 
> I don't mind pulling it directly, that's fine. But you are based on
> 2.6.39-rc5, you should be based on for-2.6.40/drivers (or core) instead.

Easily fixed:
 git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git for-jens/xen-blkfront

is now based on your for-2.6.40/drivers.

> If I pull the above, I end up getting all the changes from rc4..rc5 as
> well.

Ah, OK. Will make sure to check your for-2.6.40 in the future. Thanks!

  reply	other threads:[~2011-05-12 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 17:11 [GIT PULL] (xen) stable/blkfront for 2.6.40 Konrad Rzeszutek Wilk
2011-05-11 17:53 ` Jens Axboe
2011-05-12 13:27   ` Konrad Rzeszutek Wilk [this message]
2011-05-12 13:38     ` Jens Axboe

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=20110512132715.GC11649@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.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.