[Smart Lock] Extract the screenlock state to the proximity_auth component.

[Smart Lock] Extract the screenlock state to the proximity_auth component.

BUG=483276
TEST=none
R=tengs@chromium.org

Committed: https://crrev.com/0c4d95cab330375899d54a593149936f41808c93
Cr-Commit-Position: refs/heads/master@{#329553}

[Ilya Sherman, 2015-04-30 22:39:35]

The CQ bit was checked by isherman@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-04-30 22:40:41]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1113043004/1

[Ilya Sherman, 2015-04-30 22:42:03]

The CQ bit was unchecked by isherman@chromium.org

[Ilya Sherman, 2015-04-30 22:42:38]

The CQ bit was checked by isherman@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-04-30 22:43:54]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1113043004/20001

[Tim Song, 2015-04-30 23:16:56]

https://codereview.chromium.org/1113043004/diff/20001/components/proximity_au...
File components/proximity_auth/screenlock_state.h (right):

https://codereview.chromium.org/1113043004/diff/20001/components/proximity_au...
components/proximity_auth/screenlock_state.h:10: // Possible states of the
proximity auth feature.
nit: I would rephrase this to say "possible states for a user on the
lock/sign-in screen".

[Tim Song, 2015-04-30 23:17:05]

lgtm

[commit-bot: I haz the power, 2015-04-30 23:21:23]

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

[commit-bot: I haz the power, 2015-04-30 23:21:25]

Dry run: Try jobs failed on following builders:
  linux_chromium_compile_dbg_32_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Ilya Sherman, 2015-05-01 22:33:28]

https://chromiumcodereview.appspot.com/1113043004/diff/20001/components/proxi...
File components/proximity_auth/screenlock_state.h (right):

https://chromiumcodereview.appspot.com/1113043004/diff/20001/components/proxi...
components/proximity_auth/screenlock_state.h:10: // Possible states of the
proximity auth feature.
On 2015/04/30 23:16:56, Tim Song wrote:
> nit: I would rephrase this to say "possible states for a user on the
> lock/sign-in screen".

Done.

[Ilya Sherman, 2015-05-01 22:35:23]

The CQ bit was checked by isherman@chromium.org

[Ilya Sherman, 2015-05-01 22:35:23]

The patchset sent to the CQ was uploaded after l-g-t-m from tengs@chromium.org
Link to the patchset: https://codereview.chromium.org/1113043004/#ps40001
(title: "Fix unit tests compile")

[commit-bot: I haz the power, 2015-05-01 22:36:20]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1113043004/40001

[commit-bot: I haz the power, 2015-05-02 00:06:06]

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

[commit-bot: I haz the power, 2015-05-02 00:06:07]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Ilya Sherman, 2015-05-13 00:25:02]

The CQ bit was checked by isherman@chromium.org

[commit-bot: I haz the power, 2015-05-13 00:26:33]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1113043004/40001

[commit-bot: I haz the power, 2015-05-13 01:15:30]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-05-13 01:16:07]

Patchset 3 (id:??) landed as
https://crrev.com/0c4d95cab330375899d54a593149936f41808c93
Cr-Commit-Position: refs/heads/master@{#329553}