Searched +refs:selftests +refs:get +refs:reply (Results 1 – 2 of 2) sorted by relevance
68 especially for the current release and or stable trees, get to jump the queue.76 Pings to get a status update are welcome, but keep in mind the timing of the156 - selftests223 preference. E.g. having to skip one sentence to get to the context is less224 painful than having to skip three paragraphs to get to "what's changing".235 do get backported, but require explicit maintainer approval (search MANUALSEL).250 Running KVM selftests and KVM-unit-tests is also mandatory (and stating the262 Note, KVM selftests and KVM-unit-tests do have known failures. If you suspect286 that can't be well validated using existing KVM selftests and/or KVM-unit-tests289 Posting new feature development without tests to get early feedback is more[all …]
44 features get mainlined after this -- only fixes to the rc1 content are193 Generally speaking, the patches get triaged quickly (in less than310 get things done. Don't mangle whitespace, and as is common, don't395 not as a reply to the previous posting. Change log should include a link409 ``tools/testing/selftests/net`` or using the KUnit framework.441 new ``netdevsim`` features must be accompanied by selftests under442 ``tools/testing/selftests/``.
