mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Josh Cartwright <joshc@eso.teric.us>
To: barebox@lists.infradead.org
Cc: Michal Simek <monstr@monstr.eu>
Subject: [PATCH 1/5] trivial: doc: fix typos in mach-arm.dox
Date: Sat, 2 Mar 2013 18:48:17 -0600	[thread overview]
Message-ID: <bd191ce9722d99b8cc53eade80a9db75c29b0364.1362273612.git.joshc@eso.teric.us> (raw)
In-Reply-To: <cover.1362273612.git.joshc@eso.teric.us>

Signed-off-by: Josh Cartwright <joshc@eso.teric.us>
---
 arch/arm/mach-arm.dox | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/mach-arm.dox b/arch/arm/mach-arm.dox
index 758df3f..03e39ea 100644
--- a/arch/arm/mach-arm.dox
+++ b/arch/arm/mach-arm.dox
@@ -12,7 +12,7 @@ FIXME
       to: "runtime address != link address". You should only use branches and
       do not refer to fixed data. This implies the use of assembler code only.
 
-The ARM CPU starts at lable \<reset\> in one of the corresponding start-*.S
+The ARM CPU starts at label \<reset\> in one of the corresponding start-*.S
 files. After some basic hardware setup it can call a function
 \<arch_init_lowlevel\> if not disabled. This call is intended to give all
 developers a chance to use a standard reset vector file, but also do some
@@ -47,7 +47,7 @@ Lets call the new MACH new_cpu.
  - add /arch/arm/mach-new_cpu/Makfile
  - add other CPU specific code into /arch/arm/mach-new_cpu/
  - modify /arch/arm/Kconfig
- - modify /arch/arm/Makfile
+ - modify /arch/arm/Makefile
 
 @section mach_arm_architecures Architectures using ARM processors
 For details on specific architectures:
-- 
1.8.1.2



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-03-03  1:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03  1:20 [PATCH 0/5] Zynq support for barebox Josh Cartwright
2013-03-03  0:48 ` Josh Cartwright [this message]
2013-03-03  0:48 ` [PATCH 2/5] defaultenv: fixed mismatched braces in bin/boot Josh Cartwright
2013-03-03  0:48 ` [PATCH 3/5] ARM: zynq: add driver for Zynq uarts Josh Cartwright
2013-03-03  7:16   ` Antony Pavlov
2013-03-03 14:55     ` Josh Cartwright
2013-03-03 10:37   ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-03 10:37   ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-03  0:48 ` [PATCH 4/5] ARM: zynq: add support for Zynq 7000 SoC Josh Cartwright
2013-03-03  7:24   ` Antony Pavlov
2013-03-05 17:22     ` Josh Cartwright
2013-03-05 19:08       ` Sascha Hauer
2013-03-03  0:48 ` [PATCH 5/5] ARM: zynq: add support for zc702 development board Josh Cartwright
2013-03-03 10:39   ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-05 17:16     ` Josh Cartwright
2013-03-05 18:02       ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-03 14:58 ` [PATCH 0/5] Zynq support for barebox Steffen Trumtrar
2013-03-05 17:09   ` Josh Cartwright
2013-03-06 17:28     ` Steffen Trumtrar
2013-03-07 22:46       ` Josh Cartwright
2013-03-08  6:39         ` Steffen Trumtrar
2013-03-08 12:20           ` Michal Simek
2013-03-08 19:31             ` Steffen Trumtrar
2013-03-08 16:10           ` Josh Cartwright
2013-03-08 16:11             ` Steffen Trumtrar
2013-03-08 16:10           ` Jean-Christophe PLAGNIOL-VILLARD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd191ce9722d99b8cc53eade80a9db75c29b0364.1362273612.git.joshc@eso.teric.us \
    --to=joshc@eso.teric.us \
    --cc=barebox@lists.infradead.org \
    --cc=monstr@monstr.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox