diff options
| author |   Daniel Schultz <d.schultz@phytec.de> | 2017-03-20 13:18:51 +0100 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-03-21 22:43:03 +0000 |
| commit | 8341ee45d721cf07b19d50c249bb3a77ef1bf100 (patch) | |
| tree | 05396de21b2c2e1cb15ab4de2905f9fa7eb449bb /oe-init-build-env | |
| parent | fb9fdd7a74917cdcab039aa3a9a9944b18246fea (diff) | |
| download | openembedded-core-8341ee45d721cf07b19d50c249bb3a77ef1bf100.tar.gz | |
e2fsprogs: Fix wrong error code after optimization
fsck.ext will return an error code of 1 if a file systems was checked
and successfully repaired. Even when an optimization was performed it
will return this error code.
This patch will change the error code to 0 if only optimizations had
changed the file systems.
The reason for this patch is a question I asked at the ext4 ML:
http://www.spinics.net/lists/linux-ext4/msg55700.html
Backport from git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
Based on commit bf9f3b6d5b10d19218b4ed904c12b22e36ec57dd
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'oe-init-build-env')
0 files changed, 0 insertions, 0 deletions