Lines Matching full:changes
76 merge window, the ``net-next`` tree will be closed - no new changes/features.
134 Changes requested patch has not passed the review, new revision is expected
135 with appropriate code and commit message changes
143 requested changes, accepted or rejected the patch
167 the mailing list. For example to mark a series as Changes Requested
170 pw-bot: changes-requested
172 As a result the bot will set the entire series to Changes Requested.
216 Changes requested
219 Patches :ref:`marked<patch_status>` as ``Changes Requested`` need
288 Co-posting changes to user space components
295 When user space tools reside in the kernel repo itself all changes
315 Preparing changes
410 to the previous posting (see :ref:`Changes requested`).
418 At the very minimum your changes must survive an ``allyesconfig`` and an
425 You are expected to test your changes on top of the relevant networking