aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/sh
diff options
context:
space:
mode:
authorUwe Kleine-König <zeisberg@informatik.uni-freiburg.de>2007-02-17 13:23:03 -0500
committerAdrian Bunk <bunk@stusta.de>2007-02-17 13:23:03 -0500
commit1b3c3714cb4767d00f507cc6854d3339d82c5b9d (patch)
tree70a24435398cee2939bd71377f2fdf4d58aad8c0 /Documentation/sh
parent85d1fe095ccb6318f7a128c96630477a8859cfce (diff)
Fix typos concerning hierarchy
heirarchical, hierachical -> hierarchical heirarchy, hierachy -> hierarchy Signed-off-by: Uwe Kleine-König <zeisberg@informatik.uni-freiburg.de> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/sh')
-rw-r--r--Documentation/sh/new-machine.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/sh/new-machine.txt b/Documentation/sh/new-machine.txt
index 73988e0d112b..5482bf5d005b 100644
--- a/Documentation/sh/new-machine.txt
+++ b/Documentation/sh/new-machine.txt
@@ -17,7 +17,7 @@ of the board-specific code (with the exception of stboards) ended up
17in arch/sh/kernel/ directly, with board-specific headers ending up in 17in arch/sh/kernel/ directly, with board-specific headers ending up in
18include/asm-sh/. For the new kernel, things are broken out by board type, 18include/asm-sh/. For the new kernel, things are broken out by board type,
19companion chip type, and CPU type. Looking at a tree view of this directory 19companion chip type, and CPU type. Looking at a tree view of this directory
20heirarchy looks like the following: 20hierarchy looks like the following:
21 21
22Board-specific code: 22Board-specific code:
23 23
@@ -108,7 +108,7 @@ overloading), and you can feel free to name the directory after the family
108member itself. 108member itself.
109 109
110There are a few things that each board is required to have, both in the 110There are a few things that each board is required to have, both in the
111arch/sh/boards and the include/asm-sh/ heirarchy. In order to better 111arch/sh/boards and the include/asm-sh/ hierarchy. In order to better
112explain this, we use some examples for adding an imaginary board. For 112explain this, we use some examples for adding an imaginary board. For
113setup code, we're required at the very least to provide definitions for 113setup code, we're required at the very least to provide definitions for
114get_system_type() and platform_setup(). For our imaginary board, this 114get_system_type() and platform_setup(). For our imaginary board, this