xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Li Dongyang <lidongyang@novell.com>
Cc: xen-devel@lists.xensource.com, owen.smith@citrix.com,
	JBeulich@novell.com
Subject: Re: [PATCH V2 0/3] xen-blkfront/xen-blkback trim support
Date: Thu, 18 Aug 2011 10:56:47 -0400	[thread overview]
Message-ID: <20110818145646.GD23922@dumpdata.com> (raw)
In-Reply-To: <1313660071-25230-1-git-send-email-lidongyang@novell.com>

On Thu, Aug 18, 2011 at 05:34:28PM +0800, Li Dongyang wrote:
> Hi, List
> Here is V2 of the trim support for blkfront/blkback,
> it's now rebased on Jeremy's next-3.1 tree and has some adjustments
> according to the comments from Jan Beulich, Thanks

Great! Thanks for posting them!
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2011-08-18 14:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  9:34 [PATCH V2 0/3] xen-blkfront/xen-blkback trim support Li Dongyang
2011-08-18  9:34 ` [PATCH V2 1/3] xen-blkfront: add BLKIF_OP_TRIM and backend type flags Li Dongyang
2011-08-20  0:38   ` Jeremy Fitzhardinge
2011-08-22  9:36     ` Li Dongyang
2011-08-22 17:44       ` Jeremy Fitzhardinge
2011-08-18  9:34 ` [PATCH V2 2/3] xen-blkfront: teach blkfront driver handle trim request Li Dongyang
2011-08-18 15:05   ` Konrad Rzeszutek Wilk
2011-08-18  9:34 ` [PATCH V2 3/3] xen-blkback: handle trim request in backend driver Li Dongyang
2011-08-18 14:56   ` Konrad Rzeszutek Wilk
2011-08-22  9:43     ` Li Dongyang
2011-08-22 13:27       ` Konrad Rzeszutek Wilk
2011-08-18 14:56 ` Konrad Rzeszutek Wilk [this message]
2011-08-18 15:06 ` [PATCH V2 0/3] xen-blkfront/xen-blkback trim support Konrad Rzeszutek Wilk
2011-08-20  0:41 ` 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=20110818145646.GD23922@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=lidongyang@novell.com \
    --cc=owen.smith@citrix.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 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).