Adopted lowercase => internal pattern for LFS3_tag_* tags
This includes the mask/rm/grow bits: - LFS3_tag_RM - LFS3_tag_GROW - LFS3_tag_MASK0/2/8/12 Our in-device only handle types: - LFS3_tag_ORPHAN - LFS3_tag_TRV - LFS3_tag_UNKNOWN And in-device only tags with special behavior: - LFS3_tag_INTERNAL - LFS3_tag_RATTRS - LFS3_tag_SHRUBCOMMIT - LFS3_tag_GRMPUSH - LFS3_tag_MOVE - LFS3_tag_ATTRS Usually I'm not a big fan of case-sensitive naming patterns, but this has been useful for self-documenting what compat flags are in-device only. Might as well extend the idea to our tag definitions.
This commit is contained in:
@@ -979,7 +979,7 @@ code = '''
|
||||
// delete any bshrub/btree
|
||||
lfs3_mdir_commit(&lfs3, &file.b.h.mdir, LFS3_RATTRS(
|
||||
LFS3_RATTR(
|
||||
LFS3_TAG_RM | LFS3_TAG_MASK8 | LFS3_TAG_STRUCT, 0))) => 0;
|
||||
LFS3_tag_RM | LFS3_tag_MASK8 | LFS3_TAG_STRUCT, 0))) => 0;
|
||||
|
||||
lfs3_file_close(&lfs3, &file) => 0;
|
||||
|
||||
@@ -1107,11 +1107,11 @@ code = '''
|
||||
.bshrub=&file.b,
|
||||
.rid=0,
|
||||
.rattrs=((lfs3_rattr_t[]){
|
||||
LFS3_RATTR(LFS3_TAG_RM, -1)}),
|
||||
LFS3_RATTR(LFS3_tag_RM, -1)}),
|
||||
.rattr_count=1})))) => 0;
|
||||
lfs3_mdir_commit(&lfs3, &file.b.h.mdir, LFS3_RATTRS(
|
||||
LFS3_RATTR_SHRUB(
|
||||
LFS3_TAG_MASK8 | LFS3_TAG_BSHRUB, 0,
|
||||
LFS3_tag_MASK8 | LFS3_TAG_BSHRUB, 0,
|
||||
&file.b.b_))) => 0;
|
||||
|
||||
lfs3_file_close(&lfs3, &file) => 0;
|
||||
@@ -1231,10 +1231,10 @@ code = '''
|
||||
lfs3_rbyd_commit(&lfs3, &file.b.b.r, 0, LFS3_RATTRS(
|
||||
LFS3_RATTR_BUF(LFS3_TAG_DATA, +1, "?", 1))) => 0;
|
||||
lfs3_rbyd_commit(&lfs3, &file.b.b.r, 0, LFS3_RATTRS(
|
||||
LFS3_RATTR(LFS3_TAG_RM, -1))) => 0;
|
||||
LFS3_RATTR(LFS3_tag_RM, -1))) => 0;
|
||||
lfs3_mdir_commit(&lfs3, &file.b.h.mdir, LFS3_RATTRS(
|
||||
LFS3_RATTR_BTREE(
|
||||
LFS3_TAG_MASK8 | LFS3_TAG_BTREE, 0,
|
||||
LFS3_tag_MASK8 | LFS3_TAG_BTREE, 0,
|
||||
&file.b.b))) => 0;
|
||||
|
||||
lfs3_file_close(&lfs3, &file) => 0;
|
||||
|
||||
Reference in New Issue
Block a user