Displaying 5 results from an estimated 5 matches for "___constant_swab32".
2020 Jul 17
0
[PATCH] virtio_ring: use alloc_pages_node for NUMA-aware allocation
...<lkp at intel.com>
All error/warnings (new ones prefixed by >>):
#define __le32_to_cpu(x) __swab32((__force __u32)(__le32)(x))
^
include/uapi/linux/swab.h:119:21: note: expanded from macro '__swab32'
___constant_swab32(x) : \
^
include/uapi/linux/swab.h:19:12: note: expanded from macro '___constant_swab32'
(((__u32)(x) & (__u32)0x000000ffUL) << 24) | \
^
In file included from drivers/virtio/virtio_ring...
2020 Sep 22
0
[PATCH 3/8] vhost scsi: alloc cmds per vq instead of session
...yteorder/big_endian.h:34:59: note: expanded from macro '__le32_to_cpu'
#define __le32_to_cpu(x) __swab32((__force __u32)(__le32)(x))
^
include/uapi/linux/swab.h:119:21: note: expanded from macro '__swab32'
___constant_swab32(x) : \
^
include/uapi/linux/swab.h:20:12: note: expanded from macro '___constant_swab32'
(((__u32)(x) & (__u32)0x0000ff00UL) << 8) | \
^
In file included from drivers/vhost/scsi.c:45:...
2020 Aug 31
3
[PATCH v10 0/2] s390: virtio: let arch validate VIRTIO features
Hi all,
The goal of the series is to give a chance to the architecture
to validate VIRTIO device features.
The tests are back to virtio_finalize_features.
No more argument for the architecture callback which only reports
if the architecture needs guest memory access restrictions for
VIRTIO.
I renamed the callback to arch_has_restricted_virtio_memory_access,
and the config option to
2020 Sep 07
8
[PATCH v11 0/2] s390: virtio: let arch validate VIRTIO features
Hi all,
The goal of the series is to give a chance to the architecture
to validate VIRTIO device features.
The tests are back to virtio_finalize_features.
No more argument for the architecture callback which only reports
if the architecture needs guest memory access restrictions for
VIRTIO.
I renamed the callback to arch_has_restricted_virtio_memory_access,
the config option to
2020 Sep 07
8
[PATCH v11 0/2] s390: virtio: let arch validate VIRTIO features
Hi all,
The goal of the series is to give a chance to the architecture
to validate VIRTIO device features.
The tests are back to virtio_finalize_features.
No more argument for the architecture callback which only reports
if the architecture needs guest memory access restrictions for
VIRTIO.
I renamed the callback to arch_has_restricted_virtio_memory_access,
the config option to