Reverted LFS3_CKDATACKSUMREADS -> LFS3_CKDATACKSUMS
LFS3_CKDATACKSUMREADS is just too much. The downside is it may not be clear how LFS3_CKDATACKSUMREADS interacts with the future planned LFS3_CKREADS (LFS3_CKREADS implies LFS3_CKDATACKSUMS + LFS3_CKMETAREDUND), but on the flip side you may actually be able to type LFS3_CKDATACKSUMS on the first try.
This commit is contained in:
+7
-7
@@ -41,8 +41,8 @@
|
||||
#ifndef LFS3_CKMETAPARITY
|
||||
#define LFS3_CKMETAPARITY
|
||||
#endif
|
||||
#ifndef LFS3_CKDATACKSUMREADS
|
||||
#define LFS3_CKDATACKSUMREADS
|
||||
#ifndef LFS3_CKDATACKSUMS
|
||||
#define LFS3_CKDATACKSUMS
|
||||
#endif
|
||||
#ifndef LFS3_GC
|
||||
#define LFS3_GC
|
||||
@@ -74,8 +74,8 @@
|
||||
#ifdef LFS3_YES_CKMETAPARITY
|
||||
#define LFS3_CKMETAPARITY
|
||||
#endif
|
||||
#ifdef LFS3_YES_CKDATACKSUMREADS
|
||||
#define LFS3_CKDATACKSUMREADS
|
||||
#ifdef LFS3_YES_CKDATACKSUMS
|
||||
#define LFS3_CKDATACKSUMS
|
||||
#endif
|
||||
#ifdef LFS3_YES_GC
|
||||
#define LFS3_GC
|
||||
@@ -245,10 +245,10 @@
|
||||
#define LFS3_IFDEF_CKMETAPARITY(a, b) (b)
|
||||
#endif
|
||||
|
||||
#ifdef LFS3_CKDATACKSUMREADS
|
||||
#define LFS3_IFDEF_CKDATACKSUMREADS(a, b) (a)
|
||||
#ifdef LFS3_CKDATACKSUMS
|
||||
#define LFS3_IFDEF_CKDATACKSUMS(a, b) (a)
|
||||
#else
|
||||
#define LFS3_IFDEF_CKDATACKSUMREADS(a, b) (b)
|
||||
#define LFS3_IFDEF_CKDATACKSUMS(a, b) (b)
|
||||
#endif
|
||||
|
||||
#ifdef LFS3_GC
|
||||
|
||||
Reference in New Issue
Block a user