test.py: calculate bad patterns on change only
authorStephen Warren <swarren@nvidia.com>
Thu, 28 Jan 2016 06:57:48 +0000 (23:57 -0700)
committerSimon Glass <sjg@chromium.org>
Fri, 29 Jan 2016 04:01:24 +0000 (21:01 -0700)
commite4119ebb6dabf9bc84914b648f81c2f1b8fe76e1
tree3a1c2bf9f48d6a7487a83cb76646c72909ac0263
parent44ac762b1437b274daf9e6f2dc924088b6332a54
test.py: calculate bad patterns on change only

A future patch will use the bad_patterns array in multiple places. Rather
than duplicating the code to calculate it, or even sharing it in a
function and simply calling it redundantly when nothing has changed, only
re-calculate the list when some change is made to it. This reduces work.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
test/py/u_boot_console_base.py