aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm63xx/dts/hg556a-a.dts
diff options
context:
space:
mode:
authorHauke Mehrtens <hauke@hauke-m.de>2018-01-21 16:01:15 +0100
committerHauke Mehrtens <hauke@hauke-m.de>2018-02-13 22:24:56 +0100
commit87b35c16adcf227a853b5179890281c9977a506c (patch)
tree6757706bfcc4e02c062d32b76df02d6632cb1b61 /target/linux/brcm63xx/dts/hg556a-a.dts
parent970cbfc3074daa177c6d4868d1a94e70906d2568 (diff)
downloadupstream-87b35c16adcf227a853b5179890281c9977a506c.tar.gz
upstream-87b35c16adcf227a853b5179890281c9977a506c.tar.bz2
upstream-87b35c16adcf227a853b5179890281c9977a506c.zip
kernel: ubifs: create use file system format 4 by default
Instead of creating an ubifs file system with format version 5 by default on empty UBI volumes use the older format 4 by default. This will make it possible to mount these file systems also on older kernel versions. When a user wants to do a sysupgrade from kernel 4.14 to kernel 4.9 the old kernel has to read the file system created by the more recent kernel which currently does not work for ubifs. This fixes the problem by creating file systems which are compatible with older kernel versions by default. Kernel 4.14 will still be able to read and write UBI FS file system version 5, it will just not be used when a ubifs partition is created implicitly on an empty UBI volume. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Diffstat (limited to 'target/linux/brcm63xx/dts/hg556a-a.dts')
0 files changed, 0 insertions, 0 deletions