mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: barebox@lists.infradead.org
Cc: Rolf Evers-Fischer <embedded24@evers-fischer.de>
Subject: [PATCH] lib: parameter: fixed doku renamed ip -> ipaddr
Date: Mon, 13 Oct 2014 13:27:20 +0200	[thread overview]
Message-ID: <1413199640-6317-1-git-send-email-embedded24@evers-fischer.de> (raw)

Long time ago all ".ip" parameters have been replaced with ".ipaddr".

Signed-off-by: Rolf Evers-Fischer <embedded24@evers-fischer.de>
---
 lib/parameter.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/parameter.c b/lib/parameter.c
index 84a632c..c4c30ca 100644
--- a/lib/parameter.c
+++ b/lib/parameter.c
@@ -776,8 +776,8 @@ with device paramters. Device parameters are always strings, although there
 are functions to interpret them as something else. 'hush' users can access
 parameters as a local variable which have a dot (.) in them. So setting the
 IP address of the first ethernet device is a matter of typing
-'eth0.ip=192.168.0.7' on the console and can then be read back with
-'echo $eth0.ip'. The @ref devinfo_command command shows a summary about all
+'eth0.ipaddr=192.168.0.7' on the console and can then be read back with
+'echo $eth0.ipaddr'. The @ref devinfo_command command shows a summary about all
 devices currently present. If called with a device id as parameter it shows the
 parameters available for a device.
 
-- 
1.9.1


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

             reply	other threads:[~2014-10-13 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 11:27 Rolf Evers-Fischer [this message]
2014-10-23  5:52 ` 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=1413199640-6317-1-git-send-email-embedded24@evers-fischer.de \
    --to=embedded24@evers-fischer.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