Bug 1262557 Correct misspelled comment r=jdm
authorAndreas Farre <afarre@mozilla.com>
Wed, 06 Apr 2016 14:22:14 -0400
changeset 292274 7d110f6773c939a869789ccdecff695b5fee9a33
parent 292273 0df02c629e779e0c26125664605b36f1f5fdee30
child 292275 d335186c3be212f5922c8463be4df2a36f463ae5
push id30154
push usercbook@mozilla.com
push dateFri, 08 Apr 2016 10:00:50 +0000
treeherdermozilla-central@d9b1a9829c8e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersjdm
bugs1262557
milestone48.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1262557 Correct misspelled comment r=jdm MozReview-Commit-ID: 7snyvtPltty
dom/system/gonk/Volume.cpp
--- a/dom/system/gonk/Volume.cpp
+++ b/dom/system/gonk/Volume.cpp
@@ -51,17 +51,17 @@ VolumeObserverList Volume::sEventObserve
 // state, it gets assigned a new generation number. Whenever the state
 // of a Volume changes, we send the updated state and current generation
 // number to the main thread where it gets updated in the nsVolume.
 //
 // Since WakeLocks can only be queried from the main-thread, the
 // nsVolumeService looks for WakeLock status changes, and forwards
 // the results to the IOThread.
 //
-// If the Volume (IOThread) recieves a volume update where the generation
+// If the Volume (IOThread) receives a volume update where the generation
 // number mismatches, then the update is simply ignored.
 //
 // When a Volume (IOThread) initially becomes mounted, we assume it to
 // be locked until we get our first update from nsVolume (MainThread).
 static int32_t sMountGeneration = 0;
 
 static uint32_t sNextId = 1;