From: George Dunlap <george.dunlap@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Olaf Hering <olaf@aepfle.de>,
xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] blktap2: update connection handling to fix build with gcc5
Date: Tue, 21 Jul 2015 10:44:47 +0100 [thread overview]
Message-ID: <55AE148F.60101@citrix.com> (raw)
In-Reply-To: <1437467895.17368.78.camel@citrix.com>
On 07/21/2015 09:38 AM, Ian Campbell wrote:
> On Tue, 2015-07-21 at 00:50 -0600, Jan Beulich wrote:
>
>>> What is the longterm goal of that binary?
>>
>> It being mostly unmaintained, it's probably a candidate for removal
>> not too far in the future.
>
> George already posted a series to remove the in tree copy and treat
> blktap2 as an out of tree project[0]. That series isn't going to hit
> 4.6, obviously, but I'd expect/hope it to go in during 4.7.
Yes -- in fact, there have already been checked in block scripts which
allow one to use the out-of-tree blktap.
There are still some changes to the XenServer blktap to allow it to be
built out-of-tree -- let me know if you want those. (I'll try to
upstream them before I re-submit the blktap2 removal patches.)
-George
next prev parent reply other threads:[~2015-07-21 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 9:33 [PATCH] blktap2: update connection handling to fix build with gcc5 Olaf Hering
2015-07-20 9:09 ` Jan Beulich
2015-07-20 9:16 ` Olaf Hering
2015-07-20 9:45 ` Wei Liu
2015-07-21 6:32 ` Olaf Hering
2015-07-21 6:50 ` Jan Beulich
2015-07-21 7:04 ` Olaf Hering
2015-07-21 7:25 ` Jan Beulich
2015-07-21 8:38 ` Ian Campbell
2015-07-21 9:44 ` George Dunlap [this message]
2015-07-20 10:10 ` Jan Beulich
2015-07-20 10:23 ` M A Young
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=55AE148F.60101@citrix.com \
--to=george.dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.