Lines Matching full:changes
75 merge window, the ``net-next`` tree will be closed - no new changes/features.
133 Changes requested patch has not passed the review, new revision is expected
134 with appropriate code and commit message changes
142 requested changes, accepted or rejected the patch
166 the mailing list. For example to mark a series as Changes Requested
169 pw-bot: changes-requested
171 As a result the bot will set the entire series to Changes Requested.
215 Changes requested
218 Patches :ref:`marked<patch_status>` as ``Changes Requested`` need
287 Co-posting changes to user space components
294 When user space tools reside in the kernel repo itself all changes
317 Selftests should be part of the same series as the code changes.
320 Mixing code changes and test changes in a single commit is discouraged.
322 Preparing changes
414 This is because it is felt that the churn that such changes produce comes
433 to the previous posting (see :ref:`Changes requested`).
441 At the very minimum your changes must survive an ``allyesconfig`` and an
448 You are expected to test your changes on top of the relevant networking