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::
369    If the patch should be backported to stable, then please add a '``Cc:
375    For referring to an email posted to the kernel mailing lists, please
393    patch when applying it to your git tree. In that case, please use the
401 Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
413 Therefore, for 'volatile' documents, please create an entry in the kernel
426 Please do not expect patches to be reviewed or merged by tip
438 allowing themselves a breath. Please respect that.
499   Please refrain from using tail comments. Tail comments disturb the
579   To document functions and their arguments please use kernel-doc format
612   Please use::
672 Also please try to aggregate variables of the same type into a single
684 Please also refrain from introducing line splits in variable declarations::
703 Please use the proper u8, u16, u32, u64 types for variables which are meant
714 Please use 'unsigned int' instead of 'unsigned'.
720 Please do not use literal (hexa)decimal numbers in code or initializers.
737 Please avoid documenting struct members within the declaration, because
748 Instead, please consider using the kernel-doc format in a comment preceding
793 The 80 character rule is not a strict rule, so please use common sense when
796 When splitting function declarations or function calls, then please align
827 Please note that 'xxx_vendor\_' and 'vendor_xxx_` prefixes are not