Re: [PATCH RFC] Docs: Modernize SubmittingPatches

From: Frank Rowand
Date: Mon Dec 15 2014 - 15:29:50 EST

On 12/15/2014 7:52 AM, Jonathan Corbet wrote:
> The SubmittingPatches file still shows a lot of its roots from the era when
> we all sent stuff straight to Linus and hoped for the best. I've gone in
> and thrashed it up to reflect an age where few of us type our own "diff"
> commands anymore. Also added a section on preparing signed tags for pull
> requests.
> Signed-off-by: Jonathan Corbet <corbet@xxxxxxx>
> ---
> Documentation/SubmittingPatches | 433 ++++++++++++++++++++--------------------
> 1 file changed, 212 insertions(+), 221 deletions(-)
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 1fa1caa198eb..787d0711e18a 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -10,27 +10,48 @@ kernel, the process can sometimes be daunting if you're not familiar
> with "the system." This text is a collection of suggestions which
> can greatly increase the chances of your change being accepted.
> -Read Documentation/SubmitChecklist for a list of items to check
> -before submitting code. If you are submitting a driver, also read
> +This document contains a large number of suggestions in a relatively terse
> +format. For detailed information on how the kernel development process
> +works, see Documentation/development-process. Also, read
> +Documentation/SubmitChecklist for a list of items to check before
> +submitting code. If you are submitting a driver, also read
> Documentation/SubmittingDrivers.

If you are submitting a devicetree binding patch, also read

< snip >

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at