Skip to contentSkip to conversation

fix typo in FAQ

PATCH In review Németh Márton 2 participants 2 messages Jun 13, 2010 Memory technology devices (MTD)

lore
Share & tools
lore

Németh Márton

author
#0 lore raw

PATCH 1/1 fix typo in FAQ

Signed-off-by Márton Németh <[email protected]>

---

faq/general.xml +1 -1
index 1c0551f..be1a0d4 100644
@@ -225,7 +225,7 @@ release the chip again.
 Some NOR chips power on with all of the eraseblocks in a locked state.
 The MTD layer doesn't unlock these devices by default. If you are accessing
 these devices from user-space, you can use the <CODE>flash_unlock</CODE> tool to
-unlock the MTD device(s). If you are using the MTD device as aw rite-able root
+unlock the MTD device(s). If you are using the MTD device as a write-able root
 file-system you will either need to have the boot loader unlock the eraseblocks
 before booting the kernel, or add code to the MTD map driver for your board to
 unlock them.
#1 lore raw
Quoted 7 lines · Németh Márton
Signed-off-by Márton Németh <[email protected]>

---

faq/general.xml +0 -0
index 1c0551f..be1a0d4 100644

faq/general.xml release the chip again. · line 231

Quoted 8 lines
faq/general.xml +1 -1
@@ -225,7 +225,7 @@ release the chip again.
 Some NOR chips power on with all of the eraseblocks in a locked state.
 The MTD layer doesn't unlock these devices by default. If you are accessing
 these devices from user-space, you can use the <CODE>flash_unlock</CODE> tool to
-unlock the MTD device(s). If you are using the MTD device as aw rite-able root
+unlock the MTD device(s). If you are using the MTD device as a write-able root
 file-system you will either need to have the boot loader unlock the eraseblocks
 before booting the kernel, or add code to the MTD map driver for your board to
 unlock them.

Pushed, thank you!

Signature · 2 lines
Best Regards,
Artem Bityutskiy (Артём Битюцкий)