Add a Mojo EDK for Chrome that uses one OS pipe per message pipe.

mojo/edk/system/waiter_test_utils.h

 // Copyright 2013 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.
 
 #ifndef MOJO_EDK_SYSTEM_WAITER_TEST_UTILS_H_
 #define MOJO_EDK_SYSTEM_WAITER_TEST_UTILS_H_
 
 #include <stdint.h>
 
 #include "base/memory/ref_counted.h"
 #include "base/threading/simple_thread.h"
 #include "mojo/edk/system/dispatcher.h"
 #include "mojo/edk/system/handle_signals_state.h"
 #include "mojo/edk/system/waiter.h"
 #include "mojo/public/c/system/types.h"
 #include "mojo/public/cpp/system/macros.h"
 
 namespace mojo {
-namespace system {
+namespace edk {
 namespace test {
 
 // This is a very simple thread that has a |Waiter|, on which it waits
 // indefinitely (and records the result). It will create and initialize the
 // |Waiter| on creation, but the caller must start the thread with |Start()|. It
 // will join the thread on destruction.
 //
 // One usually uses it like:
 //
 //    MojoResult result;
@@ skipping 61 matching lines @@
   MojoResult* const result_out_;
   uint32_t* const context_out_;
   HandleSignalsState* const signals_state_out_;
 
   Waiter waiter_;
 
   MOJO_DISALLOW_COPY_AND_ASSIGN(WaiterThread);
 };
 
 }  // namespace test
-}  // namespace system
+}  // namespace edk
 }  // namespace mojo
 
 #endif  // MOJO_EDK_SYSTEM_WAITER_TEST_UTILS_H_