Fix Beamforming not getting enabled on Swanky

Fix Beamforming not getting enabled on Swanky

The official build returned a different board name with pattern "swanky*".

BUG=467643
Committed: https://crrev.com/4ea04e04f6268db33c586af89f445ab215963d95
Cr-Commit-Position: refs/heads/master@{#327098}

[aluebs-chromium, 2015-04-27 18:09:18]

aluebs@chromium.org changed reviewers:
+ ajm@chromium.org, dalecurtis@chromium.org

[aluebs-chromium, 2015-04-27 18:09:18]

I could not test this, since if I build or use test images I don't get this bug.
But I am pretty sure this is going to fix it, since I greped the binaries and
found that the board name in test images was "swanky" while in official builds
"swanky*".

[ajm, 2015-04-27 18:19:32]

lgtm

Once you've verified this on Canary, can you open a bug to request a merge to
Beta? (and even possibly Stable, but I doubt that will be approved)

[aluebs-chromium, 2015-04-27 18:21:06]

On 2015/04/27 18:19:32, ajm wrote:
> lgtm
> 
> Once you've verified this on Canary, can you open a bug to request a merge to
> Beta? (and even possibly Stable, but I doubt that will be approved)

Sure, I will.

[aluebs-chromium, 2015-04-27 18:21:09]

The CQ bit was checked by aluebs@chromium.org

[DaleCurtis, 2015-04-27 18:21:34]

lgtm

[commit-bot: I haz the power, 2015-04-27 18:21:42]

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

[commit-bot: I haz the power, 2015-04-27 19:12:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-27 19:13:27]

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