Lines Matching full:please

25      overall x86 maintainers.  Please Cc the overall x86 maintainers on
31      team. Please always Cc the Linux Kernel mailing list (LKML)
120 'genirq/core:'. Please do not use file names or complete file paths as
247 subject line, please use the format 'function_name()'. Omitting the
293    Please say instead::
367    If the patch should be backported to stable, then please add a '``Cc:
374    please use the lore.kernel.org redirector URL::
385 Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
397 Therefore, for 'volatile' documents, please create an entry in the kernel
410 Please do not expect large patch series to be handled during the merge
419 allowing themselves a breath. Please respect that.
483   Please refrain from using tail comments. Tail comments disturb the
535   To document functions and their arguments please use kernel-doc format
568   Please use::
628 Also please try to aggregate variables of the same type into a single
640 Please also refrain from introducing line splits in variable declarations::
659 Please use the proper u8, u16, u32, u64 types for variables which are meant
670 Please use 'unsigned int' instead of 'unsigned'.
676 Please do not use literal (hexa)decimal numbers in code or initializers.
693 Please avoid documenting struct members within the declaration, because
704 Instead, please consider using the kernel-doc format in a comment preceding
749 The 80 character rule is not a strict rule, so please use common sense when
752 When splitting function declarations or function calls, then please align
783 Please note that 'xxx_vendor\_' and 'vendor_xxx_` prefixes are not