Commit 44127c58 authored by Kubernetes Submit Queue's avatar Kubernetes Submit Queue Committed by GitHub

Merge pull request #40055 from StudyNick/zte-20170118

Automatic merge from submit-queue error word dummyController Struct comment "disonnected " is error word WaitForCacheSync method comment "contoller" is error word
parents 73fb9781 77cbdddb
...@@ -96,7 +96,7 @@ type InformerSynced func() bool ...@@ -96,7 +96,7 @@ type InformerSynced func() bool
const syncedPollPeriod = 100 * time.Millisecond const syncedPollPeriod = 100 * time.Millisecond
// WaitForCacheSync waits for caches to populate. It returns true if it was successful, false // WaitForCacheSync waits for caches to populate. It returns true if it was successful, false
// if the contoller should shutdown // if the controller should shutdown
func WaitForCacheSync(stopCh <-chan struct{}, cacheSyncs ...InformerSynced) bool { func WaitForCacheSync(stopCh <-chan struct{}, cacheSyncs ...InformerSynced) bool {
err := wait.PollUntil(syncedPollPeriod, err := wait.PollUntil(syncedPollPeriod,
func() (bool, error) { func() (bool, error) {
...@@ -150,7 +150,7 @@ type sharedIndexInformer struct { ...@@ -150,7 +150,7 @@ type sharedIndexInformer struct {
} }
// dummyController hides the fact that a SharedInformer is different from a dedicated one // dummyController hides the fact that a SharedInformer is different from a dedicated one
// where a caller can `Run`. The run method is disonnected in this case, because higher // where a caller can `Run`. The run method is disconnected in this case, because higher
// level logic will decide when to start the SharedInformer and related controller. // level logic will decide when to start the SharedInformer and related controller.
// Because returning information back is always asynchronous, the legacy callers shouldn't // Because returning information back is always asynchronous, the legacy callers shouldn't
// notice any change in behavior. // notice any change in behavior.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment