intel/quark: Fix assert check

Having an assignment in assert does not make sense. This seems like it
was intended to check if chip is always same as segments->chip.

Change-Id: I297d9e76a0404a1f510d43f8b9c39e96b557689f
Reported-by: Coverity ID 1357439
Signed-off-by: Furquan Shaikh <furquan@google.com>
Reviewed-on: https://review.coreboot.org/16219
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Lee Leahy <leroy.p.leahy@intel.com>
This commit is contained in:
Furquan Shaikh 2016-08-14 21:59:03 -07:00 committed by Lee Leahy
parent 363526cfb8
commit 5ff952259a
1 changed files with 1 additions and 1 deletions

View File

@ -101,7 +101,7 @@ int platform_i2c_transfer(unsigned bus, struct i2c_seg *segments, int count)
length = segments->len;
ASSERT (buffer != NULL);
ASSERT (length >= 1);
ASSERT (segments->chip = chip);
ASSERT (segments->chip == chip);
if (segments->read) {
/* Place read commands into the FIFO */