projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f652e9d) | patch
f2fs: use unlikely for release case
authorLiFan <fanofcode.li@samsung.com>
Tue, 5 Dec 2017 08:38:01 +0000 (16:38 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Wed, 3 Jan 2018 03:27:30 +0000 (19:27 -0800)
commitfab2adee36039cdc2002ba3fe3a416c3f1bc6b52
tree2a5916b9c99cf68ab6b63c2435c58258a6733912tree | snapshot
parentf652e9d988d6b4d2a81c920374431a73b70090fdcommit | diff
f2fs: use unlikely for release case

Since the variable release is only nonzero when another unlikely
case occurs, use unlikely() on it seems logical.

Signed-off-by: Fan li <fanofcode.li@samsung.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/f2fs.h diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)