Linus complains the author didn’t submit the patch to some places for public comments and testing BEFORE requesting a merge.
Although a reasonable expectation, I can’t find anything about this on the kernel.org docs for posting patches. They seem to imply that you just check and verify your patch before submitting it on the kernel mailing list, but that’s it. I didn’t see any mentions of mailing lists explicitly for feedbacks or other conventions.
Testing infrastructure would help for sure, but it’s not necessarily the lack of infra that’s causing trouble.
Linus complains the author didn’t submit the patch to some places for public comments and testing BEFORE requesting a merge.
It sounds like he expects something like
Although a reasonable expectation, I can’t find anything about this on the kernel.org docs for posting patches. They seem to imply that you just check and verify your patch before submitting it on the kernel mailing list, but that’s it. I didn’t see any mentions of mailing lists explicitly for feedbacks or other conventions.