Sjur Brændeland writes:
>> Sjur Brændeland 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
Sjur Brændeland sjurb...@gmail.com writes:
Sjur Brændeland sjurb...@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
> Sjur Brændeland 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
Sjur Brændeland sjurb...@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
Sjur Brændeland 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
Sjur Brændeland sjurb...@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
Hi Rusty,
On Wed, Feb 13, 2013 at 11:16 AM, Rusty Russell wrote:
> Sjur BRENDELAND writes:
>>> > +static inline void ctx_prep_iov(struct cfv_napi_context *ctx)
>>> > +{
>>> > + if (ctx->riov.allocated) {
>>> > + kfree(ctx->riov.iov);
>>> > + ctx->riov.iov = NULL;
>>> > +
Sjur BRENDELAND writes:
> Hi Rusty,
>
>> From: Rusty Russell [mailto:ru...@rustcorp.com.au]
>> sjur.brandel...@stericsson.com writes:
>> > +struct cfv_napi_context {
>> > + struct vringh_kiov riov;
>> > + unsigned short head;
>> > +};
>>
>> Usually we use an int, and -1. I imagine it'll take
Sjur BRENDELAND sjur.brandel...@stericsson.com writes:
Hi Rusty,
From: Rusty Russell [mailto:ru...@rustcorp.com.au]
sjur.brandel...@stericsson.com writes:
+struct cfv_napi_context {
+ struct vringh_kiov riov;
+ unsigned short head;
+};
Usually we use an int, and -1. I imagine
Hi Rusty,
On Wed, Feb 13, 2013 at 11:16 AM, Rusty Russell ru...@rustcorp.com.au wrote:
Sjur BRENDELAND sjur.brandel...@stericsson.com writes:
+static inline void ctx_prep_iov(struct cfv_napi_context *ctx)
+{
+ if (ctx-riov.allocated) {
+ kfree(ctx-riov.iov);
+
Hi Rusty,
> From: Rusty Russell [mailto:ru...@rustcorp.com.au]
> sjur.brandel...@stericsson.com writes:
> > From: Vikram ARV
> >
> > Add the the Virtio shared memory driver for STE Modems.
> > caif_virtio is implemented utilizing the virtio framework
> > for data transport and is managed with
Hi Rusty,
From: Rusty Russell [mailto:ru...@rustcorp.com.au]
sjur.brandel...@stericsson.com writes:
From: Vikram ARV vikram@stericsson.com
Add the the Virtio shared memory driver for STE Modems.
caif_virtio is implemented utilizing the virtio framework
for data transport and is
sjur.brandel...@stericsson.com writes:
> From: Vikram ARV
>
> Add the the Virtio shared memory driver for STE Modems.
> caif_virtio is implemented utilizing the virtio framework
> for data transport and is managed with the remoteproc frameworks.
>
> The Virtio queue is used for transmitting data
From: Vikram ARV
Add the the Virtio shared memory driver for STE Modems.
caif_virtio is implemented utilizing the virtio framework
for data transport and is managed with the remoteproc frameworks.
The Virtio queue is used for transmitting data to the modem, and
the new vringh implementation is
From: Vikram ARV vikram@stericsson.com
Add the the Virtio shared memory driver for STE Modems.
caif_virtio is implemented utilizing the virtio framework
for data transport and is managed with the remoteproc frameworks.
The Virtio queue is used for transmitting data to the modem, and
the new
sjur.brandel...@stericsson.com writes:
From: Vikram ARV vikram@stericsson.com
Add the the Virtio shared memory driver for STE Modems.
caif_virtio is implemented utilizing the virtio framework
for data transport and is managed with the remoteproc frameworks.
The Virtio queue is used for
16 matches
Mail list logo
