From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen-blkback: advertise indirect segment support earlier
Date: Wed, 10 Feb 2016 13:27:08 +0100 [thread overview]
Message-ID: <56BB2C9C.4040001@citrix.com> (raw)
In-Reply-To: <56BB2A8202000078000D07C8@prv-mh.provo.novell.com>
El 10/2/16 a les 12:18, Jan Beulich ha escrit:
> There's no reason to defer this until the connect phase, and in fact
> there are frontend implementations expecting this to be available
> earlier. Move it into the probe function.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Looks fine.
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
The same should be done for "feature-persistent" AFAICT.
Roger.
next prev parent reply other threads:[~2016-02-10 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:18 [PATCH] xen-blkback: advertise indirect segment support earlier Jan Beulich
2016-02-10 12:27 ` Roger Pau Monné [this message]
2016-02-15 17:39 ` 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=56BB2C9C.4040001@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xenproject.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 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).