mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 1/5] Documentation: booting linux: improve wording
Date: Tue,  9 Feb 2016 17:01:20 +0100	[thread overview]
Message-ID: <1455033684-21067-1-git-send-email-r.schwebel@pengutronix.de> (raw)

'bootm' is the lowlevel boot command, in contrast to 'boot', which is
more highlevel.

Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
 Documentation/user/booting-linux.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index 5b021f0..98628fa 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -6,7 +6,7 @@ Booting Linux
 Introduction
 ------------
 
-The basic boot command in barebox is :ref:`command_bootm`. This command
+The lowlevel boot command in barebox is :ref:`command_bootm`. This command
 can be used directly, but there is also a :ref:`command_boot` command
 which offers additional features like a boot sequence which tries to
 boot different entries until one succeeds.
@@ -14,7 +14,7 @@ boot different entries until one succeeds.
 The bootm command
 -----------------
 
-The :ref:`command_bootm` command is the basic boot command. Depending on the
+The :ref:`command_bootm` command is the lowlevel boot command. Depending on the
 architecture the bootm command handles different image types. On ARM the
 following images are supported:
 
-- 
2.7.0.rc3


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

             reply	other threads:[~2016-02-09 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 16:01 Robert Schwebel [this message]
2016-02-09 16:01 ` [PATCH 2/5] Documentation: m25p80: include in documentation Robert Schwebel
2016-02-09 16:01 ` [PATCH 3/5] Documentation: user manual: include documentation for remote-control Robert Schwebel
2016-02-09 16:01 ` [PATCH 4/5] ratp: remove unused ratp_close command Robert Schwebel
2016-02-09 16:01 ` [PATCH 5/5] Documentation: commands: remove autogenerated directory on mrproper Robert Schwebel
2016-02-10  7:20 ` [PATCH 1/5] Documentation: booting linux: improve wording Sascha Hauer

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=1455033684-21067-1-git-send-email-r.schwebel@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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