From 5ff952259ad631e24b4cb1573fe2f6c99d879e7a Mon Sep 17 00:00:00 2001 From: Furquan Shaikh Date: Sun, 14 Aug 2016 21:59:03 -0700 Subject: 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 Reviewed-on: https://review.coreboot.org/16219 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel Reviewed-by: Aaron Durbin Reviewed-by: Lee Leahy --- src/soc/intel/quark/i2c.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/soc/intel/quark') diff --git a/src/soc/intel/quark/i2c.c b/src/soc/intel/quark/i2c.c index 6465b66040..6b1f6dd46c 100644 --- a/src/soc/intel/quark/i2c.c +++ b/src/soc/intel/quark/i2c.c @@ -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 */ -- cgit v1.2.3