Lines Matching +refs:selftests +refs:get +refs:reply

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 the
156   - selftests
223 preference.  E.g. having to skip one sentence to get to the context is less
224 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 the
262 Note, KVM selftests and KVM-unit-tests do have known failures.  If you suspect
286 that can't be well validated using existing KVM selftests and/or KVM-unit-tests
289 Posting new feature development without tests to get early feedback is more
348 KVM selftests that are associated with KVM changes, e.g. regression tests for
351 failures should be ordered after the selftests updates, and vice versa, new
355 know that KVM-unit-tests is a separate repository and get confused when patches
363 in reply to the original posting (cover letter for multi-patch series).  The
372 If for some reason a patch is dropped after officially being accepted, a reply