Re: [Xen-devel] [PATCH 00/17] blktap2 related bugfix patches

[Shriram Rajagopalan <rshriram@xxxxxxxxx>]

I am fine with the block Remus mods. If you are going to modify that file for COLO, you might as well maintain them, as no one seems to be using blktap2 with Remus and libxl

Shriram

On Oct 14, 2014 9:06 PM, "Wen Congyang" <wency@xxxxxxxxxxxxxx> wrote:

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.
> .
>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel