public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common: nvedit to protect additional ethernet addresses Part 1/1
Date: Thu, 04 Dec 2008 07:46:59 -0500	[thread overview]
Message-ID: <4937D143.1030902@ge.com> (raw)
In-Reply-To: <4937cd00.hX/ek4tggr3wX3a8%stefan.althoefer@web.de>

stefan.althoefer at web.de wrote:
> [PATCH] common: nvedit to protect additional ethernet addresses
> 
> This patch adds "ethaddr1" and "ethaddr2" to the protected
> environment variables that can only be written once.
> 
> ----
> The patch is against "latest" u-boot git-repository
> 
> Please be patient if style of submission or patches are
> offending.
> 
> Signed-off-by: stefan.althoefer at web.de  (as at janz.de)
> ----
> 
> diff -uprN u-boot-orig//common/cmd_nvedit.c u-boot/common/cmd_nvedit.c
> --- u-boot-orig//common/cmd_nvedit.c	2008-12-02 17:25:31.000000000 +0100
> +++ u-boot/common/cmd_nvedit.c	2008-12-02 22:59:36.000000000 +0100
> @@ -188,6 +188,8 @@ int _do_setenv (int flag, int argc, char
>  #else
>  		    (strcmp (name, "serial#") == 0) ||
>  #endif
> +		    (strcmp (name, "ethaddr1") == 0) ||
> +		    (strcmp (name, "ethaddr2") == 0) ||
>  		    ((strcmp (name, "ethaddr") == 0)
>  #if defined(CONFIG_OVERWRITE_ETHADDR_ONCE) && defined(CONFIG_ETHADDR)
>  		     && (strcmp ((char *)env_get_addr(oldval),MK_STR(CONFIG_ETHADDR)) != 0)

Would it be better to use "strncmp (name, "ethaddr", 7)" instead of 
adding all possible enumerations of ethaddr[0-9]*?  Using strncmp() will 
match any ethaddr.* variable (a wider net than ethaddr[0-9]*, but given 
our limited environment it shouldn't matter).

gvb

  reply	other threads:[~2008-12-04 12:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 12:28 [U-Boot] [PATCH] common: nvedit to protect additional ethernet addresses Part 1/1 stefan.althoefer at web.de
2008-12-04 12:46 ` Jerry Van Baren [this message]
2008-12-04 17:57 ` Ben Warren
2008-12-04 20:48 ` Jerry Van Baren
2008-12-05 21:22   ` Stefan Althoefer
2008-12-07  0:43     ` Wolfgang Denk
2008-12-07  2:53       ` Jerry Van Baren
2008-12-07  5:47         ` Ben Warren
2008-12-07  9:33           ` Wolfgang Denk
2008-12-07 13:31     ` Stefan Althoefer
2008-12-07 16:26       ` Wolfgang Denk
2008-12-07 18:54         ` Stefan Althoefer
2008-12-07 21:25           ` Wolfgang Denk
2008-12-07 23:52             ` Stefan Althoefer
2008-12-15 22:55               ` Wolfgang Denk
2008-12-16 21:34                 ` Stefan Althoefer
2008-12-08 20:14       ` Jerry Van Baren
  -- strict thread matches above, loose matches on Subject: below --
2008-12-04 20:06 Stefan Althöfer
2008-12-04 21:06 ` Ben Warren
2008-12-15 22:56 ` Wolfgang Denk
2008-12-16 19:15   ` Stefan Althoefer
2008-12-16 19:22     ` Ben Warren
2008-12-16 20:55       ` Wolfgang Denk

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=4937D143.1030902@ge.com \
    --to=gerald.vanbaren@ge.com \
    --cc=u-boot@lists.denx.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