Buildresult: linus/arm64-allmodconfig/arm64-gcc5 built on Apr 10 2019, 20:39

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Apr 10 2019, 20:39
Duration:	0:09:00.387677
Builder:	ka4
Revision:	Bluetooth: btusb: request wake pin with NOAUTOEN (`771acc7e4a6e5dba779cb1a7fd851a164bc81033)`
Target:	linus/arm64-allmodconfig/arm64-gcc5
Branch:	linus
Compiler:	arm64-gcc5 (aarch64-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0 / GNU ld (GNU Binutils) 2.25.1)
Config:	allmodconfig (download)
Log:	Download original Possible warnings (2) drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] include/linux/spinlock.h:279:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] Full Log # git rev-parse -q --verify 771acc7e4a6e5dba779cb1a7fd851a164bc81033^{commit} 771acc7e4a6e5dba779cb1a7fd851a164bc81033 already have revision, skipping fetch # git checkout -q -f -B kisskb 771acc7e4a6e5dba779cb1a7fd851a164bc81033 # git clean -qxdf # < git log -1 # commit 771acc7e4a6e5dba779cb1a7fd851a164bc81033 # Author: Brian Norris <briannorris@chromium.org> # Date: Tue Apr 9 11:49:17 2019 -0700 # # Bluetooth: btusb: request wake pin with NOAUTOEN # # Badly-designed systems might have (for example) active-high wake pins # that default to high (e.g., because of external pull ups) until they # have an active firmware which starts driving it low. This can cause an # interrupt storm in the time between request_irq() and disable_irq(). # # We don't support shared interrupts here, so let's just pre-configure the # interrupt to avoid auto-enabling it. # # Fixes: fd913ef7ce61 ("Bluetooth: btusb: Add out-of-band wakeup support") # Fixes: 5364a0b4f4be ("arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node") # Signed-off-by: Brian Norris <briannorris@chromium.org> # Reviewed-by: Matthias Kaehlcke <mka@chromium.org> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 771acc7e4a6e5dba779cb1a7fd851a164bc81033 # < make -s -j 120 ARCH=arm64 O=/kisskb/build/linus_arm64-allmodconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- allmodconfig # make -s -j 120 ARCH=arm64 O=/kisskb/build/linus_arm64-allmodconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:40: LSE atomics not supported by binutils /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c: In function 'sh_mobile_i2c_isr': /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] pd->msg->buf[real_pos] = data; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:372:16: note: 'data' was declared here unsigned char data; ^ In file included from /kisskb/src/include/linux/rwsem.h:16:0, from /kisskb/src/include/linux/notifier.h:15, from /kisskb/src/include/linux/clk.h:17, from /kisskb/src/drivers/tty/serial/sh-sci.c:24: /kisskb/src/drivers/tty/serial/sh-sci.c: In function 'sci_dma_rx_submit': /kisskb/src/include/linux/spinlock.h:279:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] _raw_spin_unlock_irqrestore(lock, flags); \ ^ /kisskb/src/drivers/tty/serial/sh-sci.c:1353:16: note: 'flags' was declared here unsigned long flags; ^ Completed OK # rm -rf /kisskb/build/linus_arm64-allmodconfig_arm64-gcc5.4 # Build took: 0:09:00.387677

© Michael Ellerman 2006-2018.