Skip to contentSkip to conversation

linux-next: Fixed spelling typo in types.h

PATCH In review Mark Einon 2 participants 2 messages Dec 6, 2011 – Dec 7, 2011

lore
Share & tools
lore

Mark Einon

author
#0 lore raw

PATCH 1/1 linux-next: Fixed spelling typo in types.h

Spelling change, architetures -> architectures

---
 include/linux/types.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
include/linux/types.h +1 -1
index 57a9723..cbcef6e 100644
@@ -188,7 +188,7 @@ typedef __u32 __bitwise __wsum;
  * aligned_u64 should be used in defining kernel<->userspace ABIs to avoid
  * common 32/64-bit compat problems.
  * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other
- * architectures) and to 8-byte boundaries on 64-bit architetures.  The new
+ * architectures) and to 8-byte boundaries on 64-bit architectures.  The new
  * aligned_64 type enforces 8-byte alignment so that structs containing
  * aligned_64 values have the same alignment on 32-bit and 64-bit architectures.
  * No conversions are necessary between 32-bit user-space and a 64-bit kernel.
Signature · 1 line
1.7.7.3
#1 lore raw
Quoted 3 lines · Mark Einon

Spelling change, architetures -> architectures

You should Cc: [email protected] also.
[done]

Quoted 17 lines
---
 include/linux/types.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
include/linux/types.h +1 -1
index 57a9723..cbcef6e 100644
@@ -188,7 +188,7 @@ typedef __u32 __bitwise __wsum;
  * aligned_u64 should be used in defining kernel<->userspace ABIs to avoid
  * common 32/64-bit compat problems.
  * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other
- * architectures) and to 8-byte boundaries on 64-bit architetures.  The new
+ * architectures) and to 8-byte boundaries on 64-bit architectures.  The new
  * aligned_64 type enforces 8-byte alignment so that structs containing
  * aligned_64 values have the same alignment on 32-bit and 64-bit architectures.
  * No conversions are necessary between 32-bit user-space and a 64-bit kernel.
Signature · 2 lines
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***