Lines Matching refs:with
37 3) Has been carefully reviewed with respect to relevant ``Kconfig``
38 combinations. This is very hard to get right with testing---brainpower
52 4) All new module parameters are documented with ``MODULE_PARM_DESC()``
62 Check your code with tools
65 1) Check for trivial violations with the patch style checker prior to
70 2) Check cleanly with sparse.
82 a) with applicable or modified ``CONFIG`` options ``=y``, ``=m``, and
98 3) Newly-added code has been compiled with ``gcc -W`` (use
104 then test multiple builds with the related ``Kconfig`` symbols disabled
110 ``CONFIG_NET``, ``CONFIG_INET=n`` (but latter with ``CONFIG_NET=y``).
115 1) Has been tested with ``CONFIG_PREEMPT``, ``CONFIG_DEBUG_PREEMPT``,
121 2) Has been build- and runtime tested with and without ``CONFIG_SMP`` and
124 3) All codepaths have been exercised with all lockdep features enabled.
126 4) Has been checked with injection of at least slab and page-allocation
131 5) Tested with the most recent tag of linux-next to make sure that it still
132 works with all of the other queued patches and various changes in the VM,