Revert of fAddedToCache doesn't need to be atomic. (patchset #1 id:1 of https://coder...
authormtklein <mtklein@google.com>
Wed, 25 Feb 2015 16:27:41 +0000 (08:27 -0800)
committerCommit bot <commit-bot@chromium.org>
Wed, 25 Feb 2015 16:27:41 +0000 (08:27 -0800)
commit61010772e59638ff97acb3200a4ec88aa55037a6
tree140001bc7b11e09757c309497963ec7286d56b2c
parentee2a3eaf996826ec603748c7f79d4d6b5cf0ecc3
Revert of fAddedToCache doesn't need to be atomic. (patchset #1 id:1 of https://codereview.chromium.org/960573002/)

Reason for revert:
Yes it does.  notifyAddedToCache() must be thread-safe.

Original issue's description:
> fAddedToCache doesn't need to be atomic.
>
> It's only ever read or set from non-threadsafe methods.
>
> BUG=skia:
>
> Committed: https://skia.googlesource.com/skia/+/fbe0edfec4fed2a09e12b049d527d280f16e75b3

TBR=reed@google.com,mtklein@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=skia:

Review URL: https://codereview.chromium.org/959763002
include/core/SkPixelRef.h
src/core/SkPixelRef.cpp