xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	Jiang Yunhong <yunhong.jiang@intel.com>,
	Dong Eddie <eddie.dong@intel.com>,
	xen devel <xen-devel@lists.xen.org>,
	Yang Hongyang <yanghy@cn.fujitsu.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH 00/17] blktap2 related bugfix patches
Date: Wed, 15 Oct 2014 09:05:29 +0800	[thread overview]
Message-ID: <543DC859.1080207@cn.fujitsu.com> (raw)
In-Reply-To: <21565.17844.525542.420665@mariner.uk.xensource.com>

On 10/14/2014 11:48 PM, Ian Jackson wrote:
> Wen Congyang writes ("[PATCH 00/17] blktap2 related bugfix patches"):
>> These bugs are found when we implement COLO, or rebase
>> COLO to upstream xen. They are independent patches, so
>> post them in separate series.
> 
> blktap2 is unmaintained AFAICT.
> 
> In the last year there has been only one commit which shows evidence
> of someone caring even slightly about tools/blktap2/.  The last
> substantial attention was in March 2013.
> 
> (I'm disregarding commits which touch tools/blktap2/ to fix up compile
> problems with new compilers, sort out build system and file
> rearrangements, etc.)
> 
> The file you are touching in your 01/17 was last edited (by anyone, at
> all) in January 2010.
> 
> Under the circumstances, we should probably take all these changes
> without looking for anyone to ack them.
> 
> Perhaps you would like to become the maintainers of blktap2 ? :-)

Hmm, I don't have any knowledge about disk format, but blktap2 have
such codes(For example: block-vhd.c, block-qcow.c...). I think I can
maintain the rest codes.

The block-remus related modification should be reviewed and acked by remus
maintainers.

Thanks
Wen Congyang

> 
> Ian.
> .
> 

  reply	other threads:[~2014-10-15  1:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  2:13 [PATCH 00/17] blktap2 related bugfix patches Wen Congyang
2014-10-14  2:13 ` [PATCH 01/17] tools: blktap2: dynamic allocate aio_requests to avoid -EBUSY error Wen Congyang
2014-10-14  2:13 ` [PATCH 02/17] tools: block-remus: pass uuid to the callback td_open Wen Congyang
2014-10-20  2:58   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 03/17] tools: block-remus: use correct way to get remus_image Wen Congyang
2014-10-20  3:02   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 04/17] tools: block-remus: fix bug in tdremus_close() Wen Congyang
2014-10-20  3:01   ` Shriram Rajagopalan
2014-10-20  3:05     ` Wen Congyang
2014-10-14  2:13 ` [PATCH 05/17] tools: block-remus: fix memory leak Wen Congyang
2014-10-20  2:33   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 06/17] tools: blktap2: return the correct dev path Wen Congyang
2014-10-14  2:13 ` [PATCH 07/17] tools: blktap2: use correct way to get free event id Wen Congyang
2014-10-14  2:13 ` [PATCH 08/17] tools: blktap2: don't return negative " Wen Congyang
2014-10-14  2:13 ` [PATCH 09/17] tools: blktap2: use correct way to define array Wen Congyang
2014-10-20  2:37   ` Shriram Rajagopalan
2014-10-20  2:52     ` Wen Congyang
2014-10-14  2:13 ` [PATCH 10/17] tools: block-remus: fix bug in ctl_request() Wen Congyang
2014-10-20  2:38   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 11/17] tools: block-remus: clean unused functions Wen Congyang
2014-10-20  3:01   ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 12/17] tools: blktap2: implement an API to create a connection asynchronously Wen Congyang
2014-10-14  2:14 ` [PATCH 13/17] tools: block-remus: connect to backup asynchronously Wen Congyang
2014-10-20  2:50   ` Shriram Rajagopalan
2014-10-20  3:00     ` Wen Congyang
2014-10-20  3:11       ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 14/17] block-remus: switch to unprotected mode before closing Wen Congyang
2014-10-20  2:51   ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 15/17] tools: blktap2: move ramdisk related codes to block-replication.c Wen Congyang
2014-10-20  2:52   ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 16/17] support blktap remus in xl Wen Congyang
2014-10-14  2:14 ` [PATCH 17/17] HACK: libxl/remus: setup and control disk replication for blktap2 backends Wen Congyang
2014-10-20  3:00   ` Shriram Rajagopalan
2014-10-20  3:09     ` Wen Congyang
2014-10-14 15:48 ` [PATCH 00/17] blktap2 related bugfix patches Ian Jackson
2014-10-15  1:05   ` Wen Congyang [this message]
2014-10-19 20:34     ` Shriram Rajagopalan
2014-10-20 14:25     ` George Dunlap
2014-10-21  2:28       ` Wen Congyang
2014-10-21  2:56       ` Wen Congyang
2014-10-21  9:55         ` George Dunlap
2014-10-21 10:07           ` M A Young
2014-10-21 10:45           ` Bob Ball
2014-10-29  5:49       ` Wen Congyang
2014-11-03  9:58         ` George Dunlap
2014-11-03 10:07           ` Wen Congyang
2014-11-05 19:25             ` Konrad Rzeszutek Wilk
2015-02-13  6:56           ` Hongyang Yang
2015-02-14 18:40             ` George Dunlap
2014-10-27 18:32 ` Konrad Rzeszutek Wilk

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=543DC859.1080207@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.com \
    --cc=yunhong.jiang@intel.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).