Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 13fce806 authored by Andrzej Zaborowski's avatar Andrzej Zaborowski Committed by Adrian Bunk
Browse files

Fix simple typos



This corrects some trivial errors in ARM docs and comments,

Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
parent 53813158
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -118,7 +118,7 @@ to store page tables. The recommended placement is 32KiB into RAM.

In either case, the following conditions must be met:

- Quiesce all DMA capable devicess so that memory does not get
- Quiesce all DMA capable devices so that memory does not get
  corrupted by bogus network packets or disk data. This will save
  you many hours of debug.

+1 −1
Original line number Diff line number Diff line
@@ -89,7 +89,7 @@ Modules
  Although modularisation is supported (and required for the FP emulator),
  each module on an ARM2/ARM250/ARM3 machine when is loaded will take
  memory up to the next 32k boundary due to the size of the pages.
  Therefore, modularisation on these machines really worth it?
  Therefore, is modularisation on these machines really worth it?

  However, ARM6 and up machines allow modules to take multiples of 4k, and
  as such Acorn RiscPCs and other architectures using these processors can
+1 −1
Original line number Diff line number Diff line
@@ -58,7 +58,7 @@ below:
 video_y

   This describes the character position of cursor on VGA console, and
   is otherwise unused. (should not used for other console types, and
   is otherwise unused. (should not be used for other console types, and
   should not be used for other purposes).

 memc_control_reg
+3 −3
Original line number Diff line number Diff line
@@ -69,13 +69,13 @@ extern unsigned long next_timer_interrupt(void);
 * @timer: the timer to be added
 *
 * The kernel will do a ->function(->data) callback from the
 * timer interrupt at the ->expired point in the future. The
 * timer interrupt at the ->expires point in the future. The
 * current time is 'jiffies'.
 *
 * The timer's ->expired, ->function (and if the handler uses it, ->data)
 * The timer's ->expires, ->function (and if the handler uses it, ->data)
 * fields must be set prior calling this function.
 *
 * Timers with an ->expired field in the past will be executed in the next
 * Timers with an ->expires field in the past will be executed in the next
 * timer tick.
 */
static inline void add_timer(struct timer_list *timer)