aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/drivers/usb/usbip/usbip_test.sh
diff options
context:
space:
mode:
authorPeter Senna Tschudin <peter.senna@gmail.com>2018-07-10 16:01:45 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-07-13 15:41:56 +0200
commit8975a68d8cbe85da10e669a7addf92cffe7f5de2 (patch)
treeba35dc66dcc73026dd74b8286ea05f6afffb1467 /tools/testing/selftests/drivers/usb/usbip/usbip_test.sh
parentusb: dwc3: gadget: remove redundant variable maxpacket (diff)
downloadlinux-dev-8975a68d8cbe85da10e669a7addf92cffe7f5de2.tar.xz
linux-dev-8975a68d8cbe85da10e669a7addf92cffe7f5de2.zip
tools: usb: ffs-test: Fix build on big endian systems
The tools/usb/ffs-test.c file defines cpu_to_le16/32 by using the C library htole16/32 function calls. However, cpu_to_le16/32 are used when initializing structures, i.e in a context where a function call is not allowed. It works fine on little endian systems because htole16/32 are defined by the C library as no-ops. But on big-endian systems, they are actually doing something, which might involve calling a function, causing build failures, such as: ffs-test.c:48:25: error: initializer element is not constant #define cpu_to_le32(x) htole32(x) ^~~~~~~ ffs-test.c:128:12: note: in expansion of macro ‘cpu_to_le32’ .magic = cpu_to_le32(FUNCTIONFS_DESCRIPTORS_MAGIC_V2), ^~~~~~~~~~~ To solve this, we code cpu_to_le16/32 in a way that allows them to be used when initializing structures. This fix was imported from meta-openembedded/android-tools/fix-big-endian-build.patch written by Thomas Petazzoni <thomas.petazzoni@free-electrons.com>. CC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/testing/selftests/drivers/usb/usbip/usbip_test.sh')
0 files changed, 0 insertions, 0 deletions