Am 04.02.2015 um 14:29 schrieb Alexander Holler:You aren't expected to do so. Code review is an integral part of the development process here, and only truly trivial patches (stuff like fixing typos in kernel messages and documentation) get merged without it. If you pay attention to the list itself, even the veteran kernel developers almost never manage to produce a patch that is deemed absolutely perfect, and end up revising things multiple times before they get merged.
I'm really sorry that I can't spend several unpaid months with reading
and understanding ever changing linux kernel sources in order to become
a Linux filesystem expert and send some fully working perfect patches
which do fix the problem in question.
And I can't spend the necessary time to play remote keyboard for kernelYou seem to fail to understand that open source development runs primarily on volunteer work (yes there are people paid to work on open source software, but that is a generally exceptional case). A large majority of the people who are kernel maintainers are donating their free time to the project.
maintainers which might be willing to explain me what has to be done
according to their view. I've already offered what I was willing to do,
for the price of having to defend myself over and over. And
unfortunately that wasn't the first time I've ended up with having to
defend myself.
My conclusion is that I'm a real fool having posted multiple timesIf you aren't serious about trying to get something into the mainline kernel, you should be tagging _all_ of the e-mails in that patch-set with [RFC] in the subject line.
patches to this list. It just doesn't make any sense and most of the
time the only reward are flames.