Searched hist:"74 d553aad7926ed05e05d9d5cff516a7b31375fc" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/include/trace/events/ |
| H A D | ext4.h | diff 74d553aad7926ed05e05d9d5cff516a7b31375fc Wed Apr 03 11:39:17 CDT 2013 Theodore Ts'o <tytso@mit.edu> ext4: collapse handling of data=ordered and data=writeback codepaths
The only difference between how we handle data=ordered and
data=writeback is a single call to ext4_jbd2_file_inode(). Eliminate
code duplication by factoring out redundant the code paths.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
|
| /openbmc/linux/fs/ext4/ |
| H A D | ext4.h | diff 74d553aad7926ed05e05d9d5cff516a7b31375fc Wed Apr 03 11:39:17 CDT 2013 Theodore Ts'o <tytso@mit.edu> ext4: collapse handling of data=ordered and data=writeback codepaths
The only difference between how we handle data=ordered and
data=writeback is a single call to ext4_jbd2_file_inode(). Eliminate
code duplication by factoring out redundant the code paths.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
|
| H A D | inode.c | diff 74d553aad7926ed05e05d9d5cff516a7b31375fc Wed Apr 03 11:39:17 CDT 2013 Theodore Ts'o <tytso@mit.edu> ext4: collapse handling of data=ordered and data=writeback codepaths
The only difference between how we handle data=ordered and
data=writeback is a single call to ext4_jbd2_file_inode(). Eliminate
code duplication by factoring out redundant the code paths.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
|