summaryrefslogtreecommitdiff
path: root/drivers/block/zram/zram_drv.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2014-11-04 22:12:25 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2014-11-04 22:12:25 +0300
commit1efa82ecb621a819b552cf541fc5169c44816a6d (patch)
tree98d339067e4bebac15cfcb4db70a879257b1bba9 /drivers/block/zram/zram_drv.h
parent980d0d51b1c9617a472b2c0fcbe33d2d15eadc4c (diff)
parente7dbb48958897c0a80b14250a981a563d9160e4d (diff)
downloadlinux-1efa82ecb621a819b552cf541fc5169c44816a6d.tar.xz
Merge tag 'ftracetest-3.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull ftracetest fix from Steven Rostedt: "Running the ftracetests on a machine that had the debugfs file system mounted in two locations caused the ftracetests to fail. This is because the ftracetests script does a grep of the /proc/mounts file to find where the debugfs file system is mounted. If it is mounted twice, then the grep returns two lines instead of just one. This causes the ftracetests to get confused and fail. Use "head -1" to only return the first mount point for debugfs" * tag 'ftracetest-3.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: ftracetest: Take the first debugfs mount found
Diffstat (limited to 'drivers/block/zram/zram_drv.h')
0 files changed, 0 insertions, 0 deletions