Move ownership of the ControllerPairingController into the WizardController.

Move ownership of the ControllerPairingController into the WizardController.

BUG=None
R=achuith@chromium.org, zelidrag@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/c60975f9cc0a4a40bd8365cf7d322926c12b2361

[Zachary Kuznia, 2014-09-03 22:00:10]

zork@chromium.org changed reviewers:
+ zelidrag@chromium.org

[Zachary Kuznia, 2014-09-03 22:00:10]

Please take a look

[zel, 2014-09-03 22:24:28]

lgtm

[achuithb, 2014-09-03 22:26:07]

achuith@chromium.org changed reviewers:
+ achuith@chromium.org

[achuithb, 2014-09-03 22:26:07]

https://codereview.chromium.org/539733002/diff/1/chrome/browser/chromeos/logi...
File chrome/browser/chromeos/login/screens/controller_pairing_screen.h (right):

https://codereview.chromium.org/539733002/diff/1/chrome/browser/chromeos/logi...
chrome/browser/chromeos/login/screens/controller_pairing_screen.h:57:
pairing_chromeos::ControllerPairingController* controller_;
Should this be a weak reference?

[Zachary Kuznia, 2014-09-04 04:21:49]

https://codereview.chromium.org/539733002/diff/1/chrome/browser/chromeos/logi...
File chrome/browser/chromeos/login/screens/controller_pairing_screen.h (right):

https://codereview.chromium.org/539733002/diff/1/chrome/browser/chromeos/logi...
chrome/browser/chromeos/login/screens/controller_pairing_screen.h:57:
pairing_chromeos::ControllerPairingController* controller_;
On 2014/09/03 22:26:07, achuithb wrote:
> Should this be a weak reference?

No, for same reason that |actor_| is not a weak pointer.  The owner of this
object also owns |controller_|, so making it a weak pointer would make it harder
to understand the ownership graph from reading this file..

[achuithb, 2014-09-04 09:01:34]

lgtm

[Zachary Kuznia, 2014-09-04 16:12:15]

The CQ bit was checked by zork@chromium.org

[commit-bot: I haz the power, 2014-09-04 16:16:28]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/zork@chromium.org/539733002/1

[commit-bot: I haz the power, 2014-09-04 18:43:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-04 18:43:13]

Try jobs failed on following builders:
  linux_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...)

[Zachary Kuznia, 2014-09-04 18:48:07]

The CQ bit was checked by zork@chromium.org

[commit-bot: I haz the power, 2014-09-04 18:50:51]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/zork@chromium.org/539733002/1

[commit-bot: I haz the power, 2014-09-04 20:52:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-04 20:52:13]

Try jobs failed on following builders:
  win_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu_triggered...)

[Zachary Kuznia, 2014-09-04 21:30:13]

Committed patchset #1 (id:1) manually as c60975f (presubmit successful).

[commit-bot: I haz the power, 2014-09-10 03:32:42]

Patchset 1 (id:??) landed as
https://crrev.com/c60975f9cc0a4a40bd8365cf7d322926c12b2361
Cr-Commit-Position: refs/heads/master@{#293337}