tree 000824460d58cc6d8901bf74840f365efd89c6a0
parent 73ecfa71e9e35568b55e00745c2dc83cde44d2d1
author Xiao Ma <xiaom@google.com> 1587016606 +0000
committer Xiao Ma <xiaom@google.com> 1587019417 +0000

Replace confirmConfiguration with updateLayer2Information.

Since updateLayer2Information has updated such BSSID, L2Key and
GroupHint information, we can check if the initial connection has
been established or L2 roaming happened with this method instead of
confirmConfiguration. Otherwise, it seems that we impose a calling
rule for the caller: *must* call updateLayer2Information first and
then confirmConfiguration followed. Ideally, we should deal with
this case only with one metohd.

Bug: 131797393
Test: atest FrameworksWifiTests

Merged-In: I623c83dbcc6b14ea59fda1d68e9b15f09fc64f06
Change-Id: I623c83dbcc6b14ea59fda1d68e9b15f09fc64f06