mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Matthias Kaehlcke <matthias@kaehlcke.net>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] fix path specs in arch/arm/mach-arm.dox
Date: Mon, 4 Jan 2010 11:12:22 +0100	[thread overview]
Message-ID: <20100104101222.GE8799@pengutronix.de> (raw)
In-Reply-To: <20091229193411.GB5093@darwin>

Hi Matthias,

On Tue, Dec 29, 2009 at 08:34:11PM +0100, Matthias Kaehlcke wrote:
> Fix incorrect path specs in the documentation for adding an ARM based
> CPU (MACH) to the tree
> 
> Signed-off-by: Matthias Kaehlcke <matthias@kaehlcke.net>

Ok, applied

Thanks,
  Sascha

> 
> --
> 
> diff --git a/arch/arm/mach-arm.dox b/arch/arm/mach-arm.dox
> index 76b6883..758df3f 100644
> --- a/arch/arm/mach-arm.dox
> +++ b/arch/arm/mach-arm.dox
> @@ -40,12 +40,12 @@ target address is the first C instruction in barebox. At this point of time:\n
>  
>  Lets call the new MACH new_cpu.
>  
> - - create a new subdirectory in /arch/arm/new_cpu
> - - create a new subdirectory in /include/asm-arm/new_cpu
> - - add CPU specific definitions into /include/asm-arm/new_cpu/
> - - add /arch/arm/new_cpu/Kconfig
> - - add /arch/arm/new_cpu/Makfile
> - - add other CPU specific code into /arch/arm/new_cpu/
> + - create a new subdirectory in /arch/arm/mach-new_cpu
> + - create a new subdirectory in /arch/arm/mach-new_cpu/include
> + - add CPU specific definitions into /arch/arm/mach-new_cpu/include
> + - add /arch/arm/mach-new_cpu/Kconfig
> + - 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
> 
> -- 
> Matthias Kaehlcke
> Embedded Linux Developer
> Barcelona
> 
>              You must have a plan. If you don't have a plan,
>                you'll become part of somebody else's plan
>                                                                  .''`.
>     using free software / Debian GNU/Linux | http://debian.org  : :'  :
>                                                                 `. `'`
> gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

      reply	other threads:[~2010-01-04 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 19:34 Matthias Kaehlcke
2010-01-04 10:12 ` Sascha Hauer [this message]

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=20100104101222.GE8799@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=matthias@kaehlcke.net \
    /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