Displaying 20 results from an estimated 20 matches for "335,13".
Did you mean:
33,13
2019 Sep 10
2
[PATCH v3 1/2] drm/virtio: Rewrite virtio_gpu_queue_ctrl_buffer using fenced version.
...ck);
- rc = virtio_gpu_queue_ctrl_buffer_locked(vgdev, vbuf);
- spin_unlock(&vgdev->ctrlq.qlock);
- return rc;
-}
-
static int virtio_gpu_queue_fenced_ctrl_buffer(struct virtio_gpu_device *vgdev,
struct virtio_gpu_vbuffer *vbuf,
struct virtio_gpu_ctrl_hdr *hdr,
@@ -335,13 +324,19 @@ static int virtio_gpu_queue_fenced_ctrl_buffer(struct virtio_gpu_device *vgdev,
goto again;
}
- if (fence)
+ if (hdr && fence)
virtio_gpu_fence_emit(vgdev, hdr, fence);
rc = virtio_gpu_queue_ctrl_buffer_locked(vgdev, vbuf);
spin_unlock(&vgdev->ctrlq.qlock)...
2019 Sep 10
2
[PATCH v3 1/2] drm/virtio: Rewrite virtio_gpu_queue_ctrl_buffer using fenced version.
...ck);
- rc = virtio_gpu_queue_ctrl_buffer_locked(vgdev, vbuf);
- spin_unlock(&vgdev->ctrlq.qlock);
- return rc;
-}
-
static int virtio_gpu_queue_fenced_ctrl_buffer(struct virtio_gpu_device *vgdev,
struct virtio_gpu_vbuffer *vbuf,
struct virtio_gpu_ctrl_hdr *hdr,
@@ -335,13 +324,19 @@ static int virtio_gpu_queue_fenced_ctrl_buffer(struct virtio_gpu_device *vgdev,
goto again;
}
- if (fence)
+ if (hdr && fence)
virtio_gpu_fence_emit(vgdev, hdr, fence);
rc = virtio_gpu_queue_ctrl_buffer_locked(vgdev, vbuf);
spin_unlock(&vgdev->ctrlq.qlock)...
2019 Oct 24
2
[PATCH V5 1/6] mdev: class id support
...nt device.
> >> * @ops: Parent device operation structure to be registered.
> >> + * @id: class id.
> >> *
> >> * Add device to list of registered parent devices.
> >> * Returns a negative value on error, otherwise 0.
> >> @@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
> >> if (ret)
> >> goto ops_create_fail;
> >>
> >> + if (!mdev->class_id) {
> >> + ret = -EINVAL;
> >> + WARN(1, "class id must be specified for device %s\n",
> >&...
2019 Oct 24
2
[PATCH V5 1/6] mdev: class id support
...nt device.
> >> * @ops: Parent device operation structure to be registered.
> >> + * @id: class id.
> >> *
> >> * Add device to list of registered parent devices.
> >> * Returns a negative value on error, otherwise 0.
> >> @@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
> >> if (ret)
> >> goto ops_create_fail;
> >>
> >> + if (!mdev->class_id) {
> >> + ret = -EINVAL;
> >> + WARN(1, "class id must be specified for device %s\n",
> >&...
2013 Apr 11
0
No subject
...; snuck in.. will take it out. Good catch!
>
>> AS_IF([test x"$OPUS_ARM_INLINE_MEDIA" = x"1"],[
>> AC_DEFINE([OPUS_ARM_INLINE_MEDIA], [1],
>> [Use ARMv6 inline asm optimizations])
>> @@ -335,13 +363,20 @@ AS_IF([test x"${enable_asm}" = x"yes"],[
>> [*** ARM assembly requires perl -- disabling optimizations])
>> asm_optimization="(missing perl dependency for ARM)"
>> ])
>> -...
2019 Oct 23
2
[PATCH V5 1/6] mdev: class id support
...a device
> * @dev: device structure representing parent device.
> * @ops: Parent device operation structure to be registered.
> + * @id: class id.
> *
> * Add device to list of registered parent devices.
> * Returns a negative value on error, otherwise 0.
> @@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
> if (ret)
> goto ops_create_fail;
>
> + if (!mdev->class_id) {
> + ret = -EINVAL;
> + WARN(1, "class id must be specified for device %s\n",
> + dev_name(dev));
Nit, dev_warn(dev, "mdev vendor...
2019 Oct 23
2
[PATCH V5 1/6] mdev: class id support
...a device
> * @dev: device structure representing parent device.
> * @ops: Parent device operation structure to be registered.
> + * @id: class id.
> *
> * Add device to list of registered parent devices.
> * Returns a negative value on error, otherwise 0.
> @@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
> if (ret)
> goto ops_create_fail;
>
> + if (!mdev->class_id) {
> + ret = -EINVAL;
> + WARN(1, "class id must be specified for device %s\n",
> + dev_name(dev));
Nit, dev_warn(dev, "mdev vendor...
2019 Oct 24
0
[PATCH V5 1/6] mdev: class id support
...* @ops: Parent device operation structure to be registered.
> > >> + * @id: class id.
> > >> *
> > >> * Add device to list of registered parent devices.
> > >> * Returns a negative value on error, otherwise 0.
> > >> @@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
> > >> if (ret)
> > >> goto ops_create_fail;
> > >>
> > >> + if (!mdev->class_id) {
> > >> + ret = -EINVAL;
> > >> + WARN(1, "class id must be specified for...
2019 Oct 23
0
[PATCH V5 1/6] mdev: class id support
...* mdev_register_device : Register a device
* @dev: device structure representing parent device.
* @ops: Parent device operation structure to be registered.
+ * @id: class id.
*
* Add device to list of registered parent devices.
* Returns a negative value on error, otherwise 0.
@@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
if (ret)
goto ops_create_fail;
+ if (!mdev->class_id) {
+ ret = -EINVAL;
+ WARN(1, "class id must be specified for device %s\n",
+ dev_name(dev));
+ goto add_fail;
+ }
+
ret = device_add(&mdev->dev);
if (ret)...
2004 Jul 09
1
passing remote ip to pam
....10.6.deborig/src/login-common/auth-connection.c dovecot-0.99.10.6/src/login-common/auth-connection.c
--- dovecot-0.99.10.6.deborig/src/login-common/auth-connection.c 2003-05-26 08:27:13.000000000 -0700
+++ dovecot-0.99.10.6/src/login-common/auth-connection.c 2004-07-08 18:33:38.000000000 -0700
@@ -335,13 +335,21 @@ int auth_init_request(enum auth_mech mec
}
void auth_continue_request(struct auth_request *request,
- const unsigned char *data, size_t data_size)
+ const unsigned char *data, size_t data_size,
+ const struct ip_addr *remote_ip)
{
struct auth_login_request_continu...
2014 Nov 21
4
[RFC PATCHv1] cover: celt_pitch_xcorr: Introduce ARM neon intrinsics
Hello,
I received feedback from engineers working on NE10 [1] that
it would be better to use NE10 [1] for FFT optimizations for
opus use cases. However, these FFT patches are currently in review
and haven't been integrated into NE10 yet.
While the FFT functions in NE10 are getting baked, I wanted
to optimize the celt_pitch_xcorr (floating point only) and use
it to introduce ARM NEON
2019 Oct 24
0
[PATCH V5 1/6] mdev: class id support
...ce structure representing parent device.
>> * @ops: Parent device operation structure to be registered.
>> + * @id: class id.
>> *
>> * Add device to list of registered parent devices.
>> * Returns a negative value on error, otherwise 0.
>> @@ -324,6 +335,13 @@ int mdev_device_create(struct kobject *kobj,
>> if (ret)
>> goto ops_create_fail;
>>
>> + if (!mdev->class_id) {
>> + ret = -EINVAL;
>> + WARN(1, "class id must be specified for device %s\n",
>> + dev_name(dev));
> Ni...
2014 Nov 21
0
[RFC PATCHv1] armv7: celt_pitch_xcorr: Introduce ARM neon intrinsics
...ation="$inline_optimization (EDSP)"
- ])
+ ]n)
AS_IF([test x"$OPUS_ARM_INLINE_MEDIA" = x"1"],[
AC_DEFINE([OPUS_ARM_INLINE_MEDIA], [1],
[Use ARMv6 inline asm optimizations])
@@ -335,13 +363,20 @@ AS_IF([test x"${enable_asm}" = x"yes"],[
[*** ARM assembly requires perl -- disabling optimizations])
asm_optimization="(missing perl dependency for ARM)"
])
- ])
+ AS_IF([test x"$OPUS_ARM_NE...
2014 Nov 28
2
[RFC PATCHv1] armv7: celt_pitch_xcorr: Introduce ARM neon intrinsics
...quot;
> - ])
> + ]n)
Buh?
> AS_IF([test x"$OPUS_ARM_INLINE_MEDIA" = x"1"],[
> AC_DEFINE([OPUS_ARM_INLINE_MEDIA], [1],
> [Use ARMv6 inline asm optimizations])
> @@ -335,13 +363,20 @@ AS_IF([test x"${enable_asm}" = x"yes"],[
> [*** ARM assembly requires perl -- disabling optimizations])
> asm_optimization="(missing perl dependency for ARM)"
> ])
> - ])
> + AS_...
2016 Jul 18
2
[PATCH] tests: Implement script to check documented tool options match actual options.
...t;-m dev[:mountpoint[:options[:fstype]]]>
+=item B<-m> dev[:mountpoint[:options[:fstype]]]
-=item B<--mount dev[:mountpoint[:options[:fstype]]]>
+=item B<--mount> dev[:mountpoint[:options[:fstype]]]
Mount the named partition or logical volume on the given mountpoint.
@@ -335,13 +335,13 @@ or if libguestfs misidentifies a filesystem.
Enable QEMU user networking in the guest.
-=item B<-N [filename=]type>
+=item B<-N> [FILENAME=]TYPE
-=item B<--new [filename=]type>
+=item B<--new> [FILENAME=]TYPE
-=item B<-N help>
+=item B<-N>...
2012 Jan 09
1
[PATCH 1/2] generator: Rename java_structs to camel_structs to better reflect their purpose
This map was originally included just for the java bindings, but is generally
useful to any binding which uses camel case by requirement or convention.
---
generator/generator_haskell.ml | 4 ++--
generator/generator_java.ml | 10 +++++-----
generator/generator_main.ml | 2 +-
generator/generator_structs.ml | 12 +++++-------
generator/generator_structs.mli | 8 ++++----
5
2019 Oct 23
10
[PATCH V5 0/6] mdev based hardware virtio offloading support
Hi all:
There are hardwares that can do virtio datapath offloading while
having its own control path. This path tries to implement a mdev based
unified API to support using kernel virtio driver to drive those
devices. This is done by introducing a new mdev transport for virtio
(virtio_mdev) and register itself as a new kind of mdev driver. Then
it provides a unified way for kernel virtio driver
2019 Oct 23
10
[PATCH V5 0/6] mdev based hardware virtio offloading support
Hi all:
There are hardwares that can do virtio datapath offloading while
having its own control path. This path tries to implement a mdev based
unified API to support using kernel virtio driver to drive those
devices. This is done by introducing a new mdev transport for virtio
(virtio_mdev) and register itself as a new kind of mdev driver. Then
it provides a unified way for kernel virtio driver
2019 Oct 17
12
[PATCH V4 0/6] mdev based hardware virtio offloading support
Hi all:
There are hardwares that can do virtio datapath offloading while
having its own control path. This path tries to implement a mdev based
unified API to support using kernel virtio driver to drive those
devices. This is done by introducing a new mdev transport for virtio
(virtio_mdev) and register itself as a new kind of mdev driver. Then
it provides a unified way for kernel virtio driver
2019 Oct 17
12
[PATCH V4 0/6] mdev based hardware virtio offloading support
Hi all:
There are hardwares that can do virtio datapath offloading while
having its own control path. This path tries to implement a mdev based
unified API to support using kernel virtio driver to drive those
devices. This is done by introducing a new mdev transport for virtio
(virtio_mdev) and register itself as a new kind of mdev driver. Then
it provides a unified way for kernel virtio driver