On Jul 30, 2014, at 11:18 AM, David Sterba <dsterba@xxxxxxx> wrote: > The flag was named EXTENT_NO_BYPASS in the original fiemap proposal[1], > but renamed to EXTENT_ENCODED afterwards. > > [1] http://article.gmane.org/gmane.comp.file-systems.ext4/8871 This patch should be landed regardless of the rest of the series, since it is fixing a bug in the current comments. Reviewed-by: Andreas Dilger <adilger@xxxxxxxxx> > Signed-off-by: David Sterba <dsterba@xxxxxxx> > --- > include/uapi/linux/fiemap.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/uapi/linux/fiemap.h b/include/uapi/linux/fiemap.h > index 0c51d617dae9..93abfcd9ac47 100644 > --- a/include/uapi/linux/fiemap.h > +++ b/include/uapi/linux/fiemap.h > @@ -51,7 +51,7 @@ struct fiemap { > #define FIEMAP_EXTENT_ENCODED 0x00000008 /* Data can not be read > * while fs is unmounted */ > #define FIEMAP_EXTENT_DATA_ENCRYPTED 0x00000080 /* Data is encrypted by fs. > - * Sets EXTENT_NO_BYPASS. */ > + * Sets EXTENT_ENCODED */ > #define FIEMAP_EXTENT_NOT_ALIGNED 0x00000100 /* Extent offsets may not be > * block aligned. */ > #define FIEMAP_EXTENT_DATA_INLINE 0x00000200 /* Data mixed with metadata. > -- > 1.8.4.5 > Cheers, Andreas
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
