Lines Matching +full:check +full:- +full:patch

3 Linux Kernel patch submission checklist
7 kernel patch submissions accepted more quickly.
10 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
28      Use ``make htmldocs`` or ``make pdfdocs`` to check the build and
31 3) Builds on multiple CPU architectures by using local cross-compile tools
34 4) ppc64 is a good architecture for cross-compilation checking because it
35    tends to use ``unsigned long`` for 64-bit quantities.
37 5) Check your patch for general style as detailed in
38    :ref:`Documentation/process/coding-style.rst <codingstyle>`.
39    Check for trivial violations with the patch style checker prior to
42    your patch.
46    ``Documentation/kbuild/kconfig-language.rst`` Menu attributes: default value.
51    combinations.  This is very hard to get right with testing -- brainpower
54 9) Check cleanly with sparse.
64 11) Include :ref:`kernel-doc <kernel_doc>` to document global  kernel APIs.
66     ``make htmldocs`` or ``make pdfdocs`` to check the
67     :ref:`kernel-doc <kernel_doc>` and fix any issues.
75 13) Has been build- and runtime tested with and without ``CONFIG_SMP`` and
83     ``Documentation/admin-guide/kernel-parameters.rst``.
90     linux-api@vger.kernel.org.
92 19) Has been checked with injection of at least slab and page-allocation
93     failures.  See ``Documentation/fault-injection/``.
95     If the new code is substantial, addition of subsystem-specific fault
98 20) Newly-added code has been compiled with ``gcc -W`` (use
99     ``make KCFLAGS=-W``).  This will generate lots of noise, but is good
102 21) Tested after it has been merged into the -mm patchset to make sure
110 23) If any ioctl's are added by the patch, then also update
111     ``Documentation/userspace-api/ioctl/ioctl-number.rst``.