From: Paul Durrant <Paul.Durrant@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Keir (Xen.org)" <keir@xen.org>, "Tim (Xen.org)" <tim@xen.org>
Subject: Re: [PATCH v4] public/io/netif.h: make control ring hash protocol more general
Date: Fri, 26 Feb 2016 16:51:35 +0000 [thread overview]
Message-ID: <12ddf5128d5145b9ad1deb88f6ad1b53@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <56D08C7302000078000D6D4B@prv-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 26 February 2016 16:34
> To: Paul Durrant
> Cc: Ian Campbell; Ian Jackson; xen-devel@lists.xenproject.org; Keir
> (Xen.org); Tim (Xen.org)
> Subject: RE: [PATCH v4] public/io/netif.h: make control ring hash protocol
> more general
>
> >>> On 26.02.16 at 14:48, <Paul.Durrant@citrix.com> wrote:
> > Ping + 1?
>
> Paul,
>
> I guess the primary problem here is that with Ian now unlikely to
> respond, no-one on the Cc list is likely to jump in. Probably you
> should resend with the Cc-s extended to the Linux and *BSD
> netback/netfront maintainers, as they're the most likely ones to
> have comments here. At least afaic, I'd make an ack dependent
> on positive feedback from at least one of them.
>
Jan,
That's my recollection. I think Wei and David V. would be best placed to give feedback; I'll add them as cc-s.
Thanks,
Paul
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-02-26 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 15:05 [PATCH v4] public/io/netif.h: make control ring hash protocol more general Paul Durrant
2016-02-22 13:05 ` Paul Durrant
2016-02-26 13:48 ` Paul Durrant
2016-02-26 16:33 ` Jan Beulich
2016-02-26 16:51 ` Paul Durrant [this message]
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=12ddf5128d5145b9ad1deb88f6ad1b53@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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).