Lines Matching full:not

13 contributing from time to time to the kernel does not need to learn and
15 do not need to spend time pointing out style issues anymore, and thus
18 .. note:: Conventions on comments and documentation are not checked by
38 individual files, and does not require a kernel configuration. Sometimes it may
47 comments are, even though they will not be rendered. This improves consistency,
64 Comments should not be used for documentation purposes: comments are intended
65 for implementation details, not users. This distinction is useful even if the
97 ``// SAFETY:`` comments are not to be confused with the ``# Safety`` sections
108 Rust kernel code is not documented like C kernel code (i.e. via kernel-doc).
122 	/// without checking that the value is not [`None`].
154 - While not shown here, if a function may panic, the conditions under which
171   writing these comments is not just a good way of documenting what has been
208 conventions, and namespacing introduced by modules and types should not be
228 ``gpio::LineDirection::In``. In particular, it should not be named
266 It makes the compiler warn if the warning was not produced. For instance, the
275 If we do not, we get a warning from the compiler::
285 This means that ``expect``\ s do not get forgotten when they are not needed, which
293 - When the lint is not needed anymore because it was expected that it would be
301 - Conditional compilation triggers the warning in some cases but not others.
303   If there are only a few cases where the warning triggers (or does not
309   triggers the warning in some cases but not in others.
311 - When code may trigger a warning for some architectures but not others, such
325 Here, function ``g()`` is dead code if ``CONFIG_X`` is not set. Can we use
338 This would emit a lint if ``CONFIG_X`` is set, since it is not dead code in that
357 	#[cfg_attr(not(CONFIG_X), expect(dead_code))]
366 (e.g. unconditionally), then it would be spotted that it is not dead code
369 Therefore, it is likely that it is not worth using conditional ``expect``\ s when