diff options
author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2009-01-06 14:40:23 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-01-06 15:59:09 -0800 |
commit | e8ea1759138d4279869f52bfb7dca8f02f8ccfe5 (patch) | |
tree | 2e59ef400c9b79af6eeb80024c3923e21c915a8a /lib/crc-ccitt.c | |
parent | 48b47c561e41525061b5bc0cfd67d6367fd11dc4 (diff) | |
download | linux-e8ea1759138d4279869f52bfb7dca8f02f8ccfe5.tar.gz linux-e8ea1759138d4279869f52bfb7dca8f02f8ccfe5.tar.bz2 linux-e8ea1759138d4279869f52bfb7dca8f02f8ccfe5.zip |
UBIFS: do not use WB_SYNC_HOLD
WB_SYNC_HOLD is going to be zapped so we should not use it. Use
%WB_SYNC_NONE instead. Here is what akpm said:
"I think I'll just switch that to WB_SYNC_NONE. The `wait==0' mode is
just an advisory thing to help the fs shove lots of data into the
queues. If some gets missed then it'll be picked up on the second
->sync_fs call, with wait==1."
Thanks to Randy Dunlap for catching this.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Cc: Nick Piggin <npiggin@suse.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/crc-ccitt.c')
0 files changed, 0 insertions, 0 deletions