[1979] 2009-02-08 Robert Millan <[email protected]>

Robert Millan <[email protected]>
Newsgroups gmane.comp.boot-loaders.grub.cvs
Message-ID <[email protected]>
Revision: 1979
          http://svn.sv.gnu.org/viewvc/?view=rev&root=grub&revision=1979
Author:   robertmh
Date:     2009-02-08 00:28:09 +0000 (Sun, 08 Feb 2009)

Log Message:
-----------
2009-02-08  Robert Millan  <[email protected]>

        Patch from Javier Mart?\195?\173n.
        * fs/ext2.c (EXT2_DRIVER_SUPPORTED_INCOMPAT): Add
        `EXT4_FEATURE_INCOMPAT_FLEX_BG'.

Modified Paths:
--------------
    trunk/grub2/ChangeLog
    trunk/grub2/fs/ext2.c

Modified: trunk/grub2/ChangeLog
===================================================================
--- trunk/grub2/ChangeLog	2009-02-07 23:38:01 UTC (rev 1978)
+++ trunk/grub2/ChangeLog	2009-02-08 00:28:09 UTC (rev 1979)
@@ -1,5 +1,11 @@
 2009-02-08  Robert Millan  <[email protected]>
 
+	Patch from Javier Martín.
+	* fs/ext2.c (EXT2_DRIVER_SUPPORTED_INCOMPAT): Add
+	`EXT4_FEATURE_INCOMPAT_FLEX_BG'.
+
+2009-02-08  Robert Millan  <[email protected]>
+
 	* fs/cpio.c: Split tar functionality to ...
 	* fs/tar.c: ... here (new file).  Update all users.
 

Modified: trunk/grub2/fs/ext2.c
===================================================================
--- trunk/grub2/fs/ext2.c	2009-02-07 23:38:01 UTC (rev 1978)
+++ trunk/grub2/fs/ext2.c	2009-02-08 00:28:09 UTC (rev 1979)
@@ -73,7 +73,7 @@
 
 /* Superblock filesystem feature flags (RW compatible)
  * A filesystem with any of these enabled can be read and written by a driver
- * that does not understand them without causing metadata/data corruption */
+ * that does not understand them without causing metadata/data corruption.  */
 #define EXT2_FEATURE_COMPAT_DIR_PREALLOC	0x0001
 #define EXT2_FEATURE_COMPAT_IMAGIC_INODES	0x0002
 #define EXT3_FEATURE_COMPAT_HAS_JOURNAL		0x0004
@@ -83,7 +83,7 @@
 /* Superblock filesystem feature flags (RO compatible)
  * A filesystem with any of these enabled can be safely read by a driver that
  * does not understand them, but should not be written to, usually because
- * additional metadata is required */
+ * additional metadata is required.  */
 #define EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER	0x0001
 #define EXT2_FEATURE_RO_COMPAT_LARGE_FILE	0x0002
 #define EXT2_FEATURE_RO_COMPAT_BTREE_DIR	0x0004
@@ -93,7 +93,7 @@
 /* Superblock filesystem feature flags (back-incompatible)
  * A filesystem with any of these enabled should not be attempted to be read
  * by a driver that does not understand them, since they usually indicate
- * metadata format changes that might confuse the reader. */
+ * metadata format changes that might confuse the reader.  */
 #define EXT2_FEATURE_INCOMPAT_COMPRESSION	0x0001
 #define EXT2_FEATURE_INCOMPAT_FILETYPE		0x0002
 #define EXT3_FEATURE_INCOMPAT_RECOVER		0x0004 /* Needs recovery */
@@ -104,17 +104,17 @@
 #define EXT4_FEATURE_INCOMPAT_FLEX_BG		0x0200
 
 /* The set of back-incompatible features this driver DOES support. Add (OR)
- * flags here as the related features are implemented into the driver */
+ * flags here as the related features are implemented into the driver.  */
 #define EXT2_DRIVER_SUPPORTED_INCOMPAT ( EXT2_FEATURE_INCOMPAT_FILETYPE \
-                                       | EXT4_FEATURE_INCOMPAT_EXTENTS )
+                                       | EXT4_FEATURE_INCOMPAT_EXTENTS  \
+                                       | EXT4_FEATURE_INCOMPAT_FLEX_BG )
 /* List of rationales for the ignored "incompatible" features:
  * needs_recovery: Not really back-incompatible - was added as such to forbid
  *                 ext2 drivers from mounting an ext3 volume with a dirty
  *                 journal because they will ignore the journal, but the next
  *                 ext3 driver to mount the volume will find the journal and
  *                 replay it, potentially corrupting the metadata written by
- *                 the ext2 drivers
- */
+ *                 the ext2 drivers. Safe to ignore for this RO driver.  */
 #define EXT2_DRIVER_IGNORED_INCOMPAT ( EXT3_FEATURE_INCOMPAT_RECOVER )
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.