From 14e7695abb6701a659b6c1f01261d281da84a231 Mon Sep 17 00:00:00 2001 From: Jan Engelhardt Date: Sun, 12 Oct 2008 15:53:01 -0400 Subject: [PATCH] --- yaml --- r: 113398 b: refs/heads/master c: f319fb8bf6899e08bdb8d1e09a4e7a129dfa2312 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/fs/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 0fec346a2c6b..73ad789fc49b 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 3244fcb1ae03362e4aa8cb1a9039fbfd61661859 +refs/heads/master: f319fb8bf6899e08bdb8d1e09a4e7a129dfa2312 diff --git a/trunk/fs/Kconfig b/trunk/fs/Kconfig index 40183d94b683..f54a157a0296 100644 --- a/trunk/fs/Kconfig +++ b/trunk/fs/Kconfig @@ -170,8 +170,8 @@ config EXT4DEV_COMPAT help Starting with 2.6.28, the name of the ext4 filesystem was renamed from ext4dev to ext4. Unfortunately there are some - lagecy userspace programs (such as klibc's fstype) have - "ext4dev" hardcoded. + legacy userspace programs (such as klibc's fstype) have + "ext4dev" hardcoded. To enable backwards compatibility so that systems that are still expecting to mount ext4 filesystems using ext4dev,