On Thu, Apr 20, 2017 at 11:03:36AM +0200, Stan Drozd wrote:
> So here we are, this is my first contribution. I looked through the file with
> ":set spell" and this seems like the only real typo. It's not much, but I've got
> more coming.
>
> Stan
>
> Signed-off-by: Stan Drozd <drozdziak1@xxxxxxxxx>
Thank you, queued for 4.13 (or whenever Jon wants to take it). Good
show on getting your first patch posted!
I reworked your subject line and commit log, please see below (and
please let me know if my reworking was in any way problematic).
The word following the ":" on the subject line must be capitalized,
and the subject line should describe the change rather than the bug.
The body of the commit log is almost optional for this type of fix,
but if present it should describe the bug and fix.
Thanx, Paul
------------------------------------------------------------------------
commit 79b64f114cbfd5daa6117c60c38b1689f6e80ee5
Author: Stan Drozd <drozdziak1@xxxxxxxxx>
Date: Thu Apr 20 11:03:36 2017 +0200
docs: Fix typo in Documentation/memory-barriers.txt
This commit changes "architecure" to the correct spelling,
"architecture".
Signed-off-by: Stan Drozd <drozdziak1@xxxxxxxxx>
Signed-off-by: Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx>
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 08329cb857ed..6805accbba4f 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -27,7 +27,7 @@ The purpose of this document is twofold:
(2) to provide a guide as to how to use the barriers that are available.
Note that an architecture can provide more than the minimum requirement
-for any particular barrier, but if the architecure provides less than
+for any particular barrier, but if the architecture provides less than
that, that architecture is incorrect.
Note also that it is possible that a barrier may be a no-op for an
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
