UPSTREAM: 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.

BUG=None
BRANCH=None
TEST=None

Signed-off-by: Furquan Shaikh <furquan@google.com>
Reviewed-on: https://review.coreboot.org/16219
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Lee Leahy <leroy.p.leahy@intel.com>

Change-Id: I297d9e76a0404a1f510d43f8b9c39e96b557689f
Reviewed-on: https://chromium-review.googlesource.com/370709
Commit-Ready: Furquan Shaikh <furquan@chromium.org>
Tested-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>

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 */