EDK: Move mutex.*, cond_var.*, and thread_annotations.h to //mojo/edk/util.

mojo/edk/util/thread_annotations.h

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Macros for static thread-safety analysis.
 //
 // These are from http://clang.llvm.org/docs/ThreadSafetyAnalysis.html (and thus
 // really derive from google3's thread_annotations.h).
 //
 // TODO(vtl): We're still using the old-fashioned, deprecated annotations
 // ("locks" instead of "capabilities"), since the new ones don't work yet (in
 // particular, |TRY_ACQUIRE()| doesn't work: b/19264527).
 // https://github.com/domokit/mojo/issues/314
 
-#ifndef MOJO_EDK_SYSTEM_THREAD_ANNOTATIONS_H_
-#define MOJO_EDK_SYSTEM_THREAD_ANNOTATIONS_H_
+#ifndef MOJO_EDK_UTIL_THREAD_ANNOTATIONS_H_
+#define MOJO_EDK_UTIL_THREAD_ANNOTATIONS_H_
 
 // Enable thread-safety attributes only with clang.
 // The attributes can be safely erased when compiling with other compilers.
 #if defined(__clang__)
 #define MOJO_THREAD_ANNOTATION_ATTRIBUTE__(x) __attribute__((x))
 #else
 #define MOJO_THREAD_ANNOTATION_ATTRIBUTE__(x)
 #endif
 
 #define MOJO_GUARDED_BY(x) MOJO_THREAD_ANNOTATION_ATTRIBUTE__(guarded_by(x))
@@ skipping 48 matching lines @@
   MOJO_THREAD_ANNOTATION_ATTRIBUTE__(no_thread_safety_analysis)
 
 // Use this in the header to annotate a function/method as not being
 // thread-safe. This is equivalent to |MOJO_NO_THREAD_SAFETY_ANALYSIS|, but
 // semantically different: it declares that the caller must abide by additional
 // restrictions. Limitation: Unfortunately, you can't apply this to a method in
 // an interface (i.e., pure virtual method) and have it applied automatically to
 // implementations.
 #define MOJO_NOT_THREAD_SAFE MOJO_NO_THREAD_SAFETY_ANALYSIS
 
-#endif  // MOJO_EDK_SYSTEM_THREAD_ANNOTATIONS_H_
+#endif  // MOJO_EDK_UTIL_THREAD_ANNOTATIONS_H_