Note also, that patches should be sent inline in the body of the message, instead of as an attachment.

quoting inline, with quoted material prefaced with '> '.

using community-preferred commenting style.

avoiding 'text-flowed' format, extraneous line breaks, line wrapping, etc.

sending in plain text (not HTML format).

Note that the tips fall into several categories:

More tips on this topic can also be found in the kernel source repository, in the file Documentation/email-clients.txt This page exists to describe ways to configure modern email clients to be well-behaved for use in participating on Linux kernel mailing lists. This is a something that many modern e-mail clients do not do by default. Also, for both humans and automated tools, it is essential in sending and reviewing patches that exact text, spacing and line endings are preserved. For example, The mailing list software for the main kernel mailing list (LKML) considers HTML to be a sign of SPAM. Many kernel community members use mail clients, mail list software or automatic email processing scripts that do not handle HTML or attachments or weird character encodings or weird e-mail formats very well.

The Linux kernel community uses a number of email lists to send patches, review patches, and discuss changes

Outlook plain text setting