Hi, > Romain Gantois (9): > dt-bindings: misc: Describe TI FPC202 dual port controller > media: i2c: ds90ub960: Replace aliased clients list with address list > media: i2c: ds90ub960: Protect alias_use_mask with a mutex > i2c: use client addresses directly in ATR interface > i2c: move ATR alias pool to a separate struct > i2c: rename field 'alias_list' of struct i2c_atr_chan to 'alias_pairs' > i2c: support per-channel ATR alias pools > i2c: Support dynamic address translation > misc: add FPC202 dual port controller driver > > .../devicetree/bindings/misc/ti,fpc202.yaml | 94 ++++ > MAINTAINERS | 7 + > drivers/i2c/i2c-atr.c | 483 ++++++++++++++------- > drivers/media/i2c/ds90ub913.c | 9 +- > drivers/media/i2c/ds90ub953.c | 9 +- > drivers/media/i2c/ds90ub960.c | 49 ++- > drivers/misc/Kconfig | 12 + > drivers/misc/Makefile | 1 + > drivers/misc/ti_fpc202.c | 438 +++++++++++++++++++ > include/linux/i2c-atr.h | 54 ++- > 10 files changed, 965 insertions(+), 191 deletions(-) how are we going to take this? I think we are at the last bits of reviews and it's time to plan merging this series. Do we need to wait for media and then take i2c? Or shall wee take everything via i2c. I had a look at the whole series and looks quite all right to me. Andi
