On Wed, Nov 11, 2020 at 05:23:25PM -0800, Prashant Malani wrote: > This patch series add plug registration support to the cros-ec-typec > driver. It also adds support for registering alternate modes for the > registered plug. These features utilize the API provided by the Type C > connector class framework. > > The first patch adds support to the connector class framework for the > number_of_alternate_modes attribute (along with the relevant ABI > documentation). > > The next two patches add plug registration, and then altmode > registration for the plugs. The latter of these two patches utilizes the > new function for plug number_of_alternate_modes introduced in the first patch. > > This series is based on top of the following branch and other patch > series (applied in the order specified): > - Branch: chrome-platform for-next [1], which is currently set to the > "Linux 5.10-rc1" tag. > - cros-ec-typec: Patch series to register PD identity information + partner altmodes[2] > - cros-ec-typec: Patch series to register cable[3] > - cros-ec-typec: Patch series to add partner number_of_altmodes[4] > > [1]: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git/log/?h=for-next > [2]: https://lore.kernel.org/lkml/20201029222738.482366-1-pmalani@xxxxxxxxxxxx/ > [3]: https://lore.kernel.org/lkml/20201106184104.939284-1-pmalani@xxxxxxxxxxxx/ > [4]: https://lore.kernel.org/lkml/20201110061535.2163599-1-pmalani@xxxxxxxxxxxx/ Ok, I'm confused. This is not the first submission of this series, as you sent out a v2 a few days before this one. And am I supposed to suck in the chrome-platform branch into the usb-next tree? What should I do here, ignore these? Merge them? I see the USB change lost the reviewer's ack as well, why? I'm going to delete all of these patches from my review queue now and wait for a resend with some clarity as to what I should do with it :) thanks, greg k-h
