xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	"jaxboe@fusionio.com" <jaxboe@fusionio.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hch@infradead.org" <hch@infradead.org>
Subject: Re: [Xen-devel] Re: [PATCH] xen block backend driver.
Date: Fri, 13 May 2011 08:06:21 +0100	[thread overview]
Message-ID: <1305270381.31488.0.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20110512210151.GA26497@dumpdata.com>

On Thu, 2011-05-12 at 22:01 +0100, Konrad Rzeszutek Wilk wrote:
> On Wed, May 11, 2011 at 04:02:12PM +0100, Ian Campbell wrote:
> > On Thu, 2011-05-05 at 19:11 +0100, Konrad Rzeszutek Wilk wrote:
> > > This is the host side counterpart to the frontend driver
> > > in drivers/block/xen-blkfront.c. The PV protocol is also implemented by
> > > frontend drivers in other OSes too, such as the BSDs and even Windows.
> > > 
> > > The patch is based on the driver from the xen.git pvops kernel tree but
> > > has been put through the checkpatch.pl wringer plus several manual
> > > cleanup passes. It has also been moved from drivers/xen/blkback to
> > > drivers/block/xen-blback.
> > > 
> > > Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > 
> > Reviewed-by: Ian Campbell <ian.campbell@citrix.com>
> > 
> > Not much to say below, mostly minor nits really.
> 
> Thanks for reviewing it. I believe I've taken all your apt comments
> in consideration. Will post the v3.2 shortly.
> 
> > > +/*
> > > + * Function to copy the from the ring buffer the 'struct blkif_request'
> > 
> > Is the blkif namespace fair game? (I was asked to change netif is all)
> 
> It is shared with the frontend driver. I can definitly change it
> but was thinking to do it once it is in the tree - that way it can
> be one patch for both of them without having to worry about carrying
> two branches for blkfront.

Sounds reasonable to me!

Ian.

  reply	other threads:[~2011-05-13  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 18:11 [PATCH v3.1] xen block backend Konrad Rzeszutek Wilk
2011-05-05 18:11 ` [PATCH] xen block backend driver Konrad Rzeszutek Wilk
2011-05-11 15:02   ` Ian Campbell
2011-05-12 21:01     ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-05-13  7:06       ` Ian Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-20 21:05 [PATCH v3] xen block backend Konrad Rzeszutek Wilk
2011-04-20 21:05 ` [PATCH] xen block backend driver Konrad Rzeszutek Wilk
2011-04-21  3:40   ` Christoph Hellwig
2011-04-21 19:03     ` [Xen-devel] " Daniel Stodden
2011-04-21 19:06       ` Christoph Hellwig
2011-04-21 19:14         ` [Xen-devel] " Daniel Stodden
2011-04-22  9:09           ` Christoph Hellwig

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=1305270381.31488.0.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=hch@infradead.org \
    --cc=jaxboe@fusionio.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.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).