From: Rusty Russell <rusty@rustcorp.com.au>
To: "Sjur Brændeland" <sjurbren@gmail.com>
Cc: Vikram ARV <vikram.arv@stericsson.com>,
Dmitry TARNYAGIN <dmitry.tarnyagin@stericsson.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Ido Yariv <ido@wizery.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Erwan YVIN <erwan.yvin@stericsson.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH vringh 2/2] caif_virtio: Introduce caif over virtio
Date: Fri, 15 Feb 2013 15:05:42 +1030 [thread overview]
Message-ID: <87bobmjish.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAJK669YQ+x5zXSZA1FQHkRrcCt+SgZP-M_ea-Ey8ziGLhq9cqQ@mail.gmail.com>
Sjur Brændeland <sjurbren@gmail.com> writes:
> How about supporting struct vringh_kiov and struct kvec as well?
> I currently get the following complaints with my V2 patch-set:
>
> drivers/net/caif/caif_virtio.c:486:2: warning: passing argument 1 of
> ‘vringh_iov_init’ from incompatible pointer type [enabled by default]
vringh_kiov_init()? Did I miss something else?
Cheers,
Rusty.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2013-02-15 4:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 11:04 [PATCH vringh 0/2] Introduce CAIF Virtio driver sjur.brandeland
2013-02-10 11:04 ` [PATCH vringh 1/2] remoteproc: Add support for vringh (Host vrings) sjur.brandeland
2013-02-10 11:04 ` [PATCH vringh 2/2] caif_virtio: Introduce caif over virtio sjur.brandeland
2013-02-11 6:57 ` Rusty Russell
2013-02-11 8:15 ` Sjur BRENDELAND
2013-02-13 10:16 ` Rusty Russell
2013-02-13 12:50 ` Sjur Brændeland
2013-02-15 4:35 ` Rusty Russell [this message]
2013-02-16 8:48 ` Sjur Brændeland
2013-02-18 22:30 ` Rusty Russell
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=87bobmjish.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=davem@davemloft.net \
--cc=dmitry.tarnyagin@stericsson.com \
--cc=erwan.yvin@stericsson.com \
--cc=ido@wizery.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sjurbren@gmail.com \
--cc=vikram.arv@stericsson.com \
--cc=virtualization@lists.linux-foundation.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).