Hi Oliver, On Tue, Jan 17, 2023 at 5:09 PM Oliver Neukum <oneukum@xxxxxxxx> wrote: > > > > On 17.01.23 07:16, Juhyung Park wrote: > > Posted a new patch: > > https://lore.kernel.org/all/20230117061046.114145-1-qkrwngud825@xxxxxxxxx/T/#u > > > > This issue has been stalled for way too long. If string-based > > comparisons are too ugly, we can improve it later when Hongling is > > more active towards this issue. > > Hi, > > very well, you really see no other solution? > If so, could you please enhance the commit log to literally state > that there is no other way to tell them apart? And then resubmit? My unit is fine and only Hongling's isn't. I'm fairly certain that this is not the best way to deal with that specific defective unit, but unless Hongling actively participates in debugging and providing more info, the affected users (who have their completely fine RTL9210 enclosure suddenly have UAS nuked, including me) suffer more and more. String-based method is the only way *I* can do to keep Hongling's working with usb-storage while restoring UAS back to the rest of the RTL9210 enclosures with limited info Hongling's supplied thus far. I'm not sure if this is worthy enough to write in the commit message, let me know what you think. Maybe link the relevant lore.kernel.org discussions directly into the commit message? Thanks, regards > > Regards > Oliver
