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

4 Linux Kernel patch submission checklist
8 kernel patch submissions accepted more quickly.
11 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
21 2) Check your patch for general style as detailed in
22    :ref:`Documentation/process/coding-style.rst <codingstyle>`.
33    ``Documentation/kbuild/kconfig-language.rst`` Menu attributes: default value.
38    combinations.  This is very hard to get right with testing---brainpower
44 1) Include :ref:`kernel-doc <kernel_doc>` to document global kernel APIs.
50    ``Documentation/admin-guide/kernel-parameters.rst``.
57    linux-[email protected].
59 6) If any ioctl's are added by the patch, then also update
60    ``Documentation/userspace-api/ioctl/ioctl-number.rst``.
62 Check your code with tools
65 1) Check for trivial violations with the patch style checker prior to
68    your patch.
70 2) Check cleanly with sparse.
90      Use ``make htmldocs`` or ``make pdfdocs`` to check the build and
93 2) Builds on multiple CPU architectures by using local cross-compile tools
95    cross-compilation checking because it tends to use ``unsigned long`` for
96    64-bit quantities.
98 3) Newly-added code has been compiled with ``gcc -W`` (use
99    ``make KCFLAGS=-W``).  This will generate lots of noise, but is good
121 2) Has been build- and runtime tested with and without ``CONFIG_SMP`` and
126 4) Has been checked with injection of at least slab and page-allocation
127    failures.  See ``Documentation/fault-injection/``.
128    If the new code is substantial, addition of subsystem-specific fault
131 5) Tested with the most recent tag of linux-next to make sure that it still