public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/8] km/common: implement boardId HWkey checks as u-boot cmd
Date: Thu, 05 May 2011 20:29:56 +0200	[thread overview]
Message-ID: <20110505182956.F39DAD60EB7@gemini.denx.de> (raw)
In-Reply-To: <4DC2AB4A.608@keymile.com>

Dear Holger Brunck,

In message <4DC2AB4A.608@keymile.com> you wrote:
> 
> > This patch has checkpatch warnings.  Please fix.
> 
> Ok the one warning that we exceed 80 characters per line is fixed, sorry for
> that. But there are two warnings remaining:
> WARNING: consider using strict_strtoul in preference to simple_strtoul
> #137: FILE: board/keymile/common/common.c:813:
> +				bid = simple_strtoul(rest, &endp, 16);
> 
> WARNING: consider using strict_strtoul in preference to simple_strtoul
> #141: FILE: board/keymile/common/common.c:817:
> +					hwkey = simple_strtoul(rest, &endp, 16);
> 
> I know that we use strict_strtoul in the same patch some lines above, but at
> this point we need *endp and we know that we got a non numeric character at the
> end. So using simple_strtoul at this point is exactly what we want here.

Well, mixing both strict_strtoul() and simple_strtoul() [without any
comment] in the same patch was what attracted my attention in the
first place.

> Is it ok to ignore this warnings and add a comment above the codeline why we use
> simple_stroul?

Indeed this needs a comment.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
f u cn rd ths, itn tyg h myxbl cd.

  reply	other threads:[~2011-05-05 18:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 11:47 [U-Boot] [PATCH v2 0/8] km/common mainlining Holger Brunck
2011-05-04 11:47 ` [U-Boot] [PATCH v2 1/8] km/common: fix initial_boot_bank for bootpackages Holger Brunck
2011-05-10 21:17   ` Wolfgang Denk
2011-05-04 11:47 ` [U-Boot] [PATCH v2 2/8] common/hush: make get_local_var visible for other users Holger Brunck
2011-05-10 21:19   ` Wolfgang Denk
2011-05-04 11:47 ` [U-Boot] [PATCH v2 3/8] km/common: implement setboardid command Holger Brunck
2011-05-10 21:20   ` Wolfgang Denk
2011-05-04 11:47 ` [U-Boot] [PATCH v2 4/8] km/common: implement boardId HWkey checks as u-boot cmd Holger Brunck
2011-05-04 22:11   ` Wolfgang Denk
2011-05-05 13:51     ` Holger Brunck
2011-05-05 18:29       ` Wolfgang Denk [this message]
2011-05-04 11:47 ` [U-Boot] [PATCH v2 5/8] km/common: fix coding style issues in generic header Holger Brunck
2011-05-10 21:21   ` Wolfgang Denk
2011-05-04 11:47 ` [U-Boot] [PATCH v2 6/8] keymile boards: move keymile specific header in subdir Holger Brunck
2011-05-10 21:22   ` Wolfgang Denk
2011-05-04 11:47 ` [U-Boot] [PATCH v2 7/8] km/common: simplify default environment Holger Brunck
2011-05-10 21:23   ` Wolfgang Denk
2011-05-10 21:24   ` Wolfgang Denk
2011-05-11  6:58     ` Holger Brunck
2011-05-11  7:43       ` Wolfgang Denk
2011-05-04 11:47 ` [U-Boot] [PATCH v2 8/8] km/common: add pnvramsize to " Holger Brunck

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=20110505182956.F39DAD60EB7@gemini.denx.de \
    --to=wd@denx.de \
    --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