# git rev-parse -q --verify fff75eb2a08c2ac96404a2d79685668f3cf5a7a3^{commit}
fff75eb2a08c2ac96404a2d79685668f3cf5a7a3
already have revision, skipping fetch
# git checkout -q -f -B kisskb fff75eb2a08c2ac96404a2d79685668f3cf5a7a3
# git clean -qxdf
# < git log -1
# commit fff75eb2a08c2ac96404a2d79685668f3cf5a7a3
# Merge: 8188fc8 b4678df1
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Mon Apr 30 16:53:40 2018 -0700
# 
#     Merge tag 'errseq-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux
#     
#     Pull errseq infrastructure fix from Jeff Layton:
#      "The PostgreSQL developers recently had a spirited discussion about the
#       writeback error handling in Linux, and reached out to us about a
#       behavoir change to the code that bit them when the errseq_t changes
#       were merged.
#     
#       When we changed to using errseq_t for tracking writeback errors, we
#       lost the ability for an application to see a writeback error that
#       occurred before the open on which the fsync was issued. This was
#       problematic for PostgreSQL which offloads fsync calls to a completely
#       separate process from the DB writers.
#     
#       This patch restores that ability. If the errseq_t value in the inode
#       does not have the SEEN flag set, then we just return 0 for the sample.
#       That ensures that any recorded error is always delivered at least
#       once.
#     
#       Note that we might still lose the error if the inode gets evicted from
#       the cache before anything can reopen it, but that was the case before
#       errseq_t was merged. At LSF/MM we had some discussion about keeping
#       inodes with unreported writeback errors around in the cache for longer
#       (possibly indefinitely), but that's really a separate problem"
#     
#     * tag 'errseq-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux:
#       errseq: Always report a writeback error once
# < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version
# < git log --format=%s --max-count=1 fff75eb2a08c2ac96404a2d79685668f3cf5a7a3
# < make -s -j 40 ARCH=arm64 O=/kisskb/build/linus_arm64-allmodconfig_arm64 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-  allmodconfig
# make -s -j 40 ARCH=arm64 O=/kisskb/build/linus_arm64-allmodconfig_arm64 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
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dtb: Warning (pci_bridge): /pcie@10003000/pci@1,0: missing bus-range for PCI bridge
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dtb: Warning (pci_bridge): /pcie@10003000/pci@2,0: missing bus-range for PCI bridge
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dtb: Warning (pci_bridge): /pcie@10003000/pci@3,0: missing bus-range for PCI bridge
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dtb: Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge'
arch/arm64/boot/dts/qcom/apq8096-db820c.dtb: Warning (pci_bridge): /soc/agnoc@0/qcom,pcie@610000: node name is not "pci" or "pcie"
arch/arm64/boot/dts/qcom/apq8096-db820c.dtb: Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge'
arch/arm64/boot/dts/qcom/msm8996-mtp.dtb: Warning (pci_bridge): /soc/agnoc@0/qcom,pcie@610000: node name is not "pci" or "pcie"
arch/arm64/boot/dts/qcom/msm8996-mtp.dtb: Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge'
/kisskb/src/drivers/isdn/hardware/eicon/message.c: In function 'sig_ind':
/kisskb/src/drivers/isdn/hardware/eicon/message.c:5985:1: warning: the frame size of 2064 bytes is larger than 2048 bytes [-Wframe-larger-than=]
 }
 ^
Completed OK
# rm -rf /kisskb/build/linus_arm64-allmodconfig_arm64
# Build took: 0:08:02.765755