Searched hist:"977767 a7" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/fs/gfs2/ |
H A D | log.h | 977767a7 Fri Oct 12 13:07:27 CDT 2018 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Clean up gfs2_is_{ordered,writeback}
The gfs2_is_ordered and gfs2_is_writeback checks are weird in that they implicitly check for !gfs2_is_jdata. This makes understanding how to use those functions correctly a challenge. Clean this up by making gfs2_is_ordered and gfs2_is_writeback take a super block instead of an inode and by removing the implicit !gfs2_is_jdata checks. Update the callers accordingly.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> 977767a7 Fri Oct 12 13:07:27 CDT 2018 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Clean up gfs2_is_{ordered,writeback} The gfs2_is_ordered and gfs2_is_writeback checks are weird in that they implicitly check for !gfs2_is_jdata. This makes understanding how to use those functions correctly a challenge. Clean this up by making gfs2_is_ordered and gfs2_is_writeback take a super block instead of an inode and by removing the implicit !gfs2_is_jdata checks. Update the callers accordingly. Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
|
H A D | inode.h | 977767a7 Fri Oct 12 13:07:27 CDT 2018 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Clean up gfs2_is_{ordered,writeback}
The gfs2_is_ordered and gfs2_is_writeback checks are weird in that they implicitly check for !gfs2_is_jdata. This makes understanding how to use those functions correctly a challenge. Clean this up by making gfs2_is_ordered and gfs2_is_writeback take a super block instead of an inode and by removing the implicit !gfs2_is_jdata checks. Update the callers accordingly.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> 977767a7 Fri Oct 12 13:07:27 CDT 2018 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Clean up gfs2_is_{ordered,writeback} The gfs2_is_ordered and gfs2_is_writeback checks are weird in that they implicitly check for !gfs2_is_jdata. This makes understanding how to use those functions correctly a challenge. Clean this up by making gfs2_is_ordered and gfs2_is_writeback take a super block instead of an inode and by removing the implicit !gfs2_is_jdata checks. Update the callers accordingly. Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
|
H A D | aops.c | 977767a7 Fri Oct 12 13:07:27 CDT 2018 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Clean up gfs2_is_{ordered,writeback}
The gfs2_is_ordered and gfs2_is_writeback checks are weird in that they implicitly check for !gfs2_is_jdata. This makes understanding how to use those functions correctly a challenge. Clean this up by making gfs2_is_ordered and gfs2_is_writeback take a super block instead of an inode and by removing the implicit !gfs2_is_jdata checks. Update the callers accordingly.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> 977767a7 Fri Oct 12 13:07:27 CDT 2018 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Clean up gfs2_is_{ordered,writeback} The gfs2_is_ordered and gfs2_is_writeback checks are weird in that they implicitly check for !gfs2_is_jdata. This makes understanding how to use those functions correctly a challenge. Clean this up by making gfs2_is_ordered and gfs2_is_writeback take a super block instead of an inode and by removing the implicit !gfs2_is_jdata checks. Update the callers accordingly. Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
|