# git rev-parse -q --verify 291d0e5d81e101392379217b06251fe8c27f1f80^{commit}
291d0e5d81e101392379217b06251fe8c27f1f80
already have revision, skipping fetch
# git checkout -q -f -B kisskb 291d0e5d81e101392379217b06251fe8c27f1f80
# git clean -qxdf
# < git log -1
# commit 291d0e5d81e101392379217b06251fe8c27f1f80
# Merge: e75417739b1d 133424a20777
# Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
# Date:   Sat Sep 29 14:52:14 2018 -0700
# 
#     Merge tag 'for-linus-20180929' of git://git.kernel.dk/linux-block
#     
#     Jens writes:
#       "Block fixes for 4.19-rc6
#     
#        A set of fixes that should go into this release. This pull request
#        contains:
#     
#        - A fix (hopefully) for the persistent grants for xen-blkfront. A
#          previous fix from this series wasn't complete, hence reverted, and
#          this one should hopefully be it. (Boris Ostrovsky)
#     
#        - Fix for an elevator drain warning with SMR devices, which is
#          triggered when you switch schedulers (Damien)
#     
#        - bcache deadlock fix (Guoju Fang)
#     
#        - Fix for the block unplug tracepoint, which has had the
#          timer/explicit flag reverted since 4.11 (Ilya)
#     
#        - Fix a regression in this series where the blk-mq timeout hook is
#          invoked with the RCU read lock held, hence preventing it from
#          blocking (Keith)
#     
#        - NVMe pull from Christoph, with a single multipath fix (Susobhan Dey)"
#     
#     * tag 'for-linus-20180929' of git://git.kernel.dk/linux-block:
#       xen/blkfront: correct purging of persistent grants
#       Revert "xen/blkfront: When purging persistent grants, keep them in the buffer"
#       blk-mq: I/O and timer unplugs are inverted in blktrace
#       bcache: add separate workqueue for journal_write to avoid deadlock
#       xen/blkfront: When purging persistent grants, keep them in the buffer
#       block: fix deadline elevator drain for zoned block devices
#       blk-mq: Allow blocking queue tag iter callbacks
#       nvme: properly propagate errors in nvme_mpath_init
# < /opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-gcc --version
# < git log --format=%s --max-count=1 291d0e5d81e101392379217b06251fe8c27f1f80
# < make -s -j 120 ARCH=microblaze O=/kisskb/build/linus_nommu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-  nommu_defconfig
# make -s -j 120 ARCH=microblaze O=/kisskb/build/linus_nommu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-  
/kisskb/src/drivers/i2c/i2c-core-base.c: In function 'i2c_generic_scl_recovery':
/kisskb/src/drivers/i2c/i2c-core-base.c:235:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized]
  if (ret == -EOPNOTSUPP)
     ^
Kernel: arch/microblaze/boot/linux.bin is ready  (#1)
Completed OK
# rm -rf /kisskb/build/linus_nommu_defconfig_microblaze
# Build took: 0:00:20.951391