A patch addressing a new USB core warning in rtl28xxu ended up causing a regression. As this was caught before the patch was committed it was superseded by a v2. Unfortunately, the first erroneous version ended up being applied to the media tree anyway. This reverts the first version of the patch and resends the second version. Mauro and Hans, I've reported this issue to you both repeatedly over the course of three weeks but you never replied to any of mails. I'm not sure what went wrong, but I would assume that regressions would be handled with a bit more urgency. Are you not receiving my mails or was this perhaps a case of it not being clear who of you should act on the reports? 2021-05-24: v1 posted https://lore.kernel.org/r/20210524110920.24599-4-johan@xxxxxxxxxx 2021-05-31: Request not apply v1 https://lore.kernel.org/r/YLSWeyy1skooTmqD@xxxxxxxxxxxxxxxxxxxx 2021-05-31: v2 posted https://lore.kernel.org/r/20210531094434.12651-4-johan@xxxxxxxxxx 2021-06-02: v1 applied to media tree and a request to drop it was sent in response to the automatic notification mail 2021-06-07: Second request to drop v1 with a question of how best to proceed to fix the regression otherwise https://lore.kernel.org/r/YL3MCGY5wTsW2kEF@xxxxxxxxxxxxxxxxxxxx Johan Johan Hovold (2): Revert "media: rtl28xxu: fix zero-length control request" media: rtl28xxu: fix zero-length control request drivers/media/usb/dvb-usb-v2/rtl28xxu.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) -- 2.31.1
