On 11/15/12 09:31, Jan Kiszka wrote: >> > I'd prefer to keep the error jump target to handle the parse error here. >> > Dumping the reset there is fine with me, but I'd prefer this event being >> > logged (trace point or stderr message or both) to ease trouble shooting >> > in case a device doesn't behave as expected. > That would be "over-logging" as we already record the individual > reasons. There is simply no code to jump to after the refactoring.
Oh, right, we trace that already. Ok then. Patch added to usb patch queue. thanks, Gerd
