tree c8bee808d95c91a6fb39999964f7961c8cbb38d7
parent 4a9ffec296fa2b5c1343e73d45fed5c48e4a39b0
author Kaushik Lingarkar <kaushikl@codeaurora.org> 1611676782 -0800
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1611676782 +0000

Update git submodules

* Update plugins/replication from branch 'stable-3.2'
  to a5636087cb17a3d4d2450736d6382da682cc1fa9
  - Merge branch 'stable-3.1' into stable-3.2
    
    * stable-3.1:
      Use volatile and AtomicIntegers to be thread safe
    
    Change-Id: I923730a525fbffb4c304ab0d23b088f5e8bfa307
    
  - Merge branch 'stable-3.0' into stable-3.1
    
    * stable-3.0:
      Use volatile and AtomicIntegers to be thread safe
    
    Change-Id: I0be6a13344043a48f2fc4a0367559f5b5f1fbca9
    
  - Merge branch 'stable-2.16' into stable-3.0
    
    * stable-2.16:
      Use volatile and AtomicIntegers to be thread safe
    
    Change-Id: I90a3e17e2f49d07707409ba390c0a6dd0501b512
    
  - Use volatile and AtomicIntegers to be thread safe
    
    Modify the fields in ReplicationState class to be volatile and
    AtomicIntegers so that changes to them are reflected to other
    threads. By not doing so, modifications made by one thread to
    these fields may not be reflected instantly depending on
    cpu caching thus resulting in incorrect state
    
    Change-Id: I76512b17c19cc68e4f1e6a5223899f9a184bb549