[db48x]

Have you even read the instructions? It answers all of those questions.

> I'd just file it at my distro and let the maintainer deal with the upstream reporting.

They even ask you to do that _in the instructions_ that you haven’t read due to laziness.

[crote]

The instructions are fifteen thousands words, and don't even answer all of those questions. That's worse than no instructions at all, if you ask me.

You'd be hard-pressed to call me "lazy", to be honest. I'm more than happy to dig into the kernel source to determine the cause of such a regression because I actually like doing that kind of thing. I've submitted several single-digit-line patches to large projects to solve exactly this kind of issue.

Spending a Saturday morning trying to figure out a kernel bug is quite enjoyable. Spending a Saturday afternoon trying to figure out how to submit a bug report or patch is not - especially when it is literally a 5-minute process for the vast majority of other software projects. If I have to deal with that much bureaucracy, I'll just keep my patch to myself.