From: David Miller <davem@davemloft.net>
To: paul.durrant@citrix.com
Cc: xen-devel@lists.xenproject.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] xen-netback: support for control ring
Date: Thu, 12 May 2016 11:52:19 -0400 (EDT) [thread overview]
Message-ID: <20160512.115219.759608823316429913.davem@davemloft.net> (raw)
In-Reply-To: <1462979790-2824-1-git-send-email-paul.durrant@citrix.com>
From: Paul Durrant <paul.durrant@citrix.com>
Date: Wed, 11 May 2016 16:16:26 +0100
> My recent patch to import an up-to-date include/xen/interface/io/netif.h
> from the Xen Project brought in the necessary definitions to support the
> new control shared ring and protocol. This patch series updates xen-netback
> to support the new ring.
I lost my copy of your V3 cover letter, so I'm replying to this one, but
be sure I tested V3 :-)
This doesn't build, please fix:
ERROR: "init_rcu_head" [drivers/net/xen-netback/xen-netback.ko] undefined!
ERROR: "destroy_rcu_head" [drivers/net/xen-netback/xen-netback.ko] undefined!
next prev parent reply other threads:[~2016-05-12 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 15:16 [PATCH net-next v2 0/4] xen-netback: support for control ring Paul Durrant
2016-05-11 15:16 ` [PATCH net-next v2 1/4] xen-netback: add control ring boilerplate Paul Durrant
2016-05-11 15:16 ` [PATCH net-next v2 2/4] xen-netback: add control protocol implementation Paul Durrant
2016-05-11 15:38 ` Paul Durrant
2016-05-11 15:16 ` [PATCH net-next v2 3/4] xen-netback: pass hash value to the frontend Paul Durrant
2016-05-11 15:16 ` [PATCH net-next v2 4/4] xen-netback: use hash value from " Paul Durrant
2016-05-12 15:52 ` David Miller [this message]
2016-05-12 15:56 ` [Xen-devel] [PATCH net-next v2 0/4] xen-netback: support for control ring Paul Durrant
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=20160512.115219.759608823316429913.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.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).