type: Rename vector_3_t to intv3_t.

Naming of many vector types and matrix types are not clear enough.
For example, we have:
  vector_3_t, which is a vector of three int.
  vec3_t, which is a vector of three float.
  size4_t, which is a vector of four size_t.
  mat33_t, which is a 3x3 matrix of float.
  matrix_3x3_t, which is a 3x3 matrix of fixed point.
Besides, we have types like int8_t, uint16_t types.

To clearly distinguished types, the CL propose to,

For vector types, naming should be `$type + 'v' + $num + '_t'`:
  vector_3_t becomes intv3_t
  vec3_t becomes floatv3_t
  vector 4 of uint16_t becomes uint16v4_t (which doesn't exist yet)

For matrix types, naming should be `mat$N$N_` + $type + '_t', where $N is the
matrix size:
  matrix_3x3_t becomes mat33_fp_t  # fp: fixed point
  mat33_t becomes mat33_float_t

TEST=make buildall -j
BUG=b:114662791

Change-Id: I865aa3ecbab6cb97f8585a081a679adf00febe1d
Signed-off-by: Yilun Lin <yllin@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1215442
Commit-Ready: Yilun Lin <yllin@chromium.org>
Tested-by: Yilun Lin <yllin@chromium.org>
Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/driver/baro_bmp280.c b/driver/baro_bmp280.c
index e6220c7e35..b622535819 100644
--- a/driver/baro_bmp280.c
+++ b/driver/baro_bmp280.c
@@ -298,7 +298,7 @@ static int bmp280_init(const struct motion_sensor_t *s)
 	return sensor_init_done(s);
 }
 
-static int bmp280_read(const struct motion_sensor_t *s, vector_3_t v)
+static int bmp280_read(const struct motion_sensor_t *s, intv3_t v)
 {
 	int ret, pres;
 	struct bmp280_drv_data_t *data = BMP280_GET_DATA(s);