# git rev-parse -q --verify 618d919cae2fcaadc752f27ddac8b939da8b441a^{commit}
618d919cae2fcaadc752f27ddac8b939da8b441a
already have revision, skipping fetch
# git checkout -q -f -B kisskb 618d919cae2fcaadc752f27ddac8b939da8b441a
# git clean -qxdf
# < git log -1
# commit 618d919cae2fcaadc752f27ddac8b939da8b441a
# Merge: 5512320c9f6f 2170a0d53bee
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Mon Apr 15 16:48:51 2019 -0700
# 
#     Merge tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
#     
#     Pull libnvdimm fixes from Dan Williams:
#      "I debated holding this back for the v5.2 merge window due to the size
#       of the "zero-key" changes, but affected users would benefit from
#       having the fixes sooner. It did not make sense to change the zero-key
#       semantic in isolation for the "secure-erase" command, but instead
#       include it for all security commands.
#     
#       The short background on the need for these changes is that some NVDIMM
#       platforms enable security with a default zero-key rather than let the
#       OS specify the initial key. This makes the security enabling that
#       landed in v5.0 unusable for some users.
#     
#       Summary:
#     
#        - Compatibility fix for nvdimm-security implementations with a
#          default zero-key.
#     
#        - Miscellaneous small fixes for out-of-bound accesses, cleanup after
#          initialization failures, and missing debug messages"
#     
#     * tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm:
#       tools/testing/nvdimm: Retain security state after overwrite
#       libnvdimm/pmem: fix a possible OOB access when read and write pmem
#       libnvdimm/security, acpi/nfit: unify zero-key for all security commands
#       libnvdimm/security: provide fix for secure-erase to use zero-key
#       libnvdimm/btt: Fix a kmemdup failure check
#       libnvdimm/namespace: Fix a potential NULL pointer dereference
#       acpi/nfit: Always dump _DSM output payload
# < /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 618d919cae2fcaadc752f27ddac8b939da8b441a
# < make -s -j 10 ARCH=arm64 O=/kisskb/build/linus_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-  defconfig
# make -s -j 10 ARCH=arm64 O=/kisskb/build/linus_arm64-defconfig_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-defconfig_arm64-gcc5.4
# Build took: 0:05:00.223174