[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <69b22028203da533392c60debbeabe6932422e98.1730874296.git.dsimic@manjaro.org>
Date: Wed, 6 Nov 2024 07:28:41 +0100
From: Dragan Simic <dsimic@...jaro.org>
To: apw@...onical.com,
joe@...ches.com,
corbet@....net
Cc: dwaipayanray1@...il.com,
lukas.bulwahn@...il.com,
workflows@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org,
wens@...e.org,
dsimic@...jaro.org
Subject: [PATCH v2 2/3] docs: submitting-patches: Reflow one short paragraph
Reflow one spotted short paragraph, to make it more consistent with the rest
of the file. No functional changes are introduced.
Signed-off-by: Dragan Simic <dsimic@...jaro.org>
---
Documentation/process/submitting-patches.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 1518bd57adab..382c49659cb9 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -202,9 +202,8 @@ Style-check your changes
------------------------
Check your patch for basic style violations, details of which can be
-found in Documentation/process/coding-style.rst.
-Failure to do so simply wastes
-the reviewers time and will get your patch rejected, probably
+found in Documentation/process/coding-style.rst. Failure to do so simply
+wastes the reviewers time and will get your patch rejected, probably
without even being read.
One significant exception is when moving code from one file to
Powered by blists - more mailing lists