From: Sascha Hauer <s.hauer@pengutronix.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH V2] Documentation: fix typos & correct symlink
Date: Thu, 25 Mar 2010 08:40:48 +0100 [thread overview]
Message-ID: <20100325074047.GA2241@pengutronix.de> (raw)
In-Reply-To: <1269436583-11896-1-git-send-email-w.sang@pengutronix.de>
On Wed, Mar 24, 2010 at 02:16:23PM +0100, Wolfram Sang wrote:
> I found the wrong symlink and activated the spell-checker while I was here.
Applied.
Sascha
>
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> ---
>
> Since V1, I dropped the "barebox's licence"-part.
>
> Documentation/barebox-main.dox | 14 +++++++-------
> 1 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/barebox-main.dox b/Documentation/barebox-main.dox
> index 743add8..01c45c1 100644
> --- a/Documentation/barebox-main.dox
> +++ b/Documentation/barebox-main.dox
> @@ -48,7 +48,7 @@ things right - without caring about losing support for old boards.
> - simulation target
> - @a barebox can be compiled to run under Linux. While this is rather useless
> in real world this is a great debugging and development aid. New features
> - can be easily developped and tested on long train journeys and started
> + can be easily developed and tested on long train journeys and started
> under gdb. There is a console driver for linux which emulates a serial
> device and a tap based ethernet driver. Linux files can be mapped to
> devices under @a barebox to emulate storage devices.
> @@ -59,7 +59,7 @@ things right - without caring about losing support for old boards.
> 'eth0.ip=192.168.0.7' or 'echo $eth0.ip'
>
> - initcalls
> - - hooks in the startup process can be archieved with *_initcall() directives
> + - hooks in the startup process can be achieved with *_initcall() directives
> in each file.
>
> - getopt
> @@ -91,7 +91,7 @@ cross_compile pointing to your architecture and compiler. For @p ARCH=sandbox
> we do not need a cross compiler so it is sufficient to specify the
> architecture:
>
> -@code # ln -s sandbox cross_arch @endcode
> +@code # ln -s arch/sandbox cross_arch @endcode
>
> In order to configure the various aspects of @a barebox, start the @a barebox
> configuration system:
> @@ -102,7 +102,7 @@ This command starts a menu box and lets you select all the different
> options available for your architecture. Once the configuration was
> finished (you can simulate this by using the standard demo config file
> with 'make sandbox_defconfig'), there is a .config file in the toplevel
> -directory of the sourcode.
> +directory of the sourcecode.
>
> Once @a barebox is configured, we can start the compilation
>
> @@ -115,7 +115,7 @@ If everything goes well, the result is a file called @p barebox:
> -rwxr-xr-x 1 rsc ptx 114073 Jun 26 22:34 barebox
> @endcode
>
> -@a barebox usually needs an environment for storing the configuation data.
> +@a barebox usually needs an environment for storing the configuration data.
> You can generate an environment using the example environment contained
> in board/sandbox/env:
>
> @@ -146,7 +146,7 @@ loaded the example environment @a barebox will show you a menu asking for
> your settings.
>
> If you have started @a barebox as root you will find a new tap device on your
> -host which you can configure using ifconfig. Once you configured @a barebox's
> +host which you can configure using ifconfig. Once you configured the
> network settings accordingly you can do a ping or tftpboot.
>
> If you have mapped a cramfs image try mounting it with
> @@ -191,7 +191,7 @@ net / -> Networking stuff
>
> scripts / -> Kconfig system
>
> -Documentation / -> Parts of the documention, also doxygen
> +Documentation / -> Parts of the documentation, also doxygen
> @endverbatim
>
> @section license barebox's License
> --
> 1.7.0
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2010-03-25 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 13:16 Wolfram Sang
2010-03-25 7:40 ` 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=20100325074047.GA2241@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=w.sang@pengutronix.de \
/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