Lines Matching full:series

67 room for the size of a series, patches that are "cache hot", etc.  Fixes,
80 on series that break the build or fail tests lead to unhappy maintainers!
98 The only exception to using ``kvm-x86/next`` as the base is if a patch/series
99 is a multi-arch series, i.e. has non-trivial modifications to common KVM code
101 arch patch/series should instead be based on a common, stable point in KVM's
103 you're unsure whether a patch/series is truly multi-arch, err on the side of
112 :ref:`maintainer-tip-coding-style`, as patches/series often touch both KVM and
211 E.g. when doing a series of "git blame", the details of each change along the
245 At a bare minimum, *all* patches in a series must build cleanly for KVM_INTEL=m
317 Do not explicitly reference bug reports, prior versions of a patch/series, etc.
319 for large series and/or when the version count gets high, and ``In-Reply-To:``
349 bug fixes, should be posted along with the KVM changes as a single series.  The
356 in a series apply on different trees.  To tie KVM-unit-tests patches back to
358 KVM patch/series in the KVM-unit-tests patch(es).
362 When a patch/series is officially accepted, a notification email will be sent
363 in reply to the original posting (cover letter for multi-patch series).  The
369 series that were not accepted need more work and should be submitted in a new