mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: paulus@samba.org, linux-kernel@vger.kernel.org, wd@denx.de
Subject: Re: [PATCH 1/3] Merge mkubootimg tool for building U-Boot images
Date: Fri, 4 Jan 2008 17:13:36 +0100	[thread overview]
Message-ID: <20080104161336.GB31026@uranus.ravnborg.org> (raw)
In-Reply-To: <20080103160244.6a28519b@zod.rchland.ibm.com>

On Thu, Jan 03, 2008 at 04:02:44PM -0600, Josh Boyer wrote:
> Several platforms require the mkimage tool to generate a uImage file that is
> used with U-Boot.  This brings the mkimage tool in-kernel to enable building
> those platforms without having mkimage externally provided.  The tool is named
> mkubootimg for better clarity.
> 
> This is currently based off of the version found in U-Boot 1.3.1.

I got following warnings:
 HOSTCC  scripts/mkubootimg/mkimage.o
scripts/mkubootimg/mkimage.c:40: warning: function declaration isn’t a prototype
scripts/mkubootimg/mkimage.c: In function ‘main’:
scripts/mkubootimg/mkimage.c:199: warning: dereferencing type-punned pointer will break strict-aliasing rules
scripts/mkubootimg/mkimage.c:216: warning: dereferencing type-punned pointer will break strict-aliasing rules

And sparse gave following warnings (with default options)
$ sparse -DUSE_HOSTCC *.c
crc32.c:154:5: warning: non-ANSI definition of function 'crc32'
/usr/include/asm/errno.h:9:4: warning: This machine appears to be neither x86_64 nor i386.
/usr/include/asm/socket.h:9:4: warning: This machine appears to be neither x86_64 nor i386.
mkimage.c:40:12: warning: non-ANSI function declaration of function '__errno_location'
mkimage.c:574:8: warning: non-ANSI function declaration of function 'usage'
mkimage.c:46:6: warning: symbol 'cmdname' was not declared. Should it be static?
mkimage.c:56:15: warning: symbol 'arch_name' was not declared. Should it be static?
mkimage.c:78:15: warning: symbol 'os_name' was not declared. Should it be static?
mkimage.c:102:15: warning: symbol 'type_name' was not declared. Should it be static?
mkimage.c:115:15: warning: symbol 'comp_name' was not declared. Should it be static?
mkimage.c:138:6: warning: symbol 'datafile' was not declared. Should it be static?
mkimage.c:139:6: warning: symbol 'imagefile' was not declared. Should it be static?
mkimage.c:141:5: warning: symbol 'dflag' was not declared. Should it be static?
mkimage.c:142:5: warning: symbol 'eflag' was not declared. Should it be static?
mkimage.c:143:5: warning: symbol 'lflag' was not declared. Should it be static?
mkimage.c:144:5: warning: symbol 'vflag' was not declared. Should it be static?
mkimage.c:145:5: warning: symbol 'xflag' was not declared. Should it be static?
mkimage.c:146:5: warning: symbol 'opt_os' was not declared. Should it be static?
mkimage.c:147:5: warning: symbol 'opt_arch' was not declared. Should it be static?
mkimage.c:148:5: warning: symbol 'opt_type' was not declared. Should it be static?
mkimage.c:149:5: warning: symbol 'opt_comp' was not declared. Should it be static?
mkimage.c:151:16: warning: symbol 'header' was not declared. Should it be static?
mkimage.c:152:16: warning: symbol 'hdr' was not declared. Should it be static?
mkimage.c:300:31: warning: Using plain integer as NULL pointer
mkimage.c:438:30: warning: Using plain integer as NULL pointer
mkimage.c:518:30: warning: Using plain integer as NULL pointer
mkimage.c:574:1: warning: symbol 'usage' was not declared. Should it be static?

Please fix and resubmit (without the sha1 files).

	Sam

  parent reply	other threads:[~2008-01-04 16:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 22:01 [PATCH 0/3] Merge mkimage tool Josh Boyer
2008-01-03 22:02 ` [PATCH 1/3] Merge mkubootimg tool for building U-Boot images Josh Boyer
2008-01-03 22:15   ` Mike Frysinger
2008-01-03 22:26     ` Josh Boyer
2008-01-03 22:33       ` Mike Frysinger
2008-01-03 22:35         ` Josh Boyer
2008-01-04 16:07           ` Sam Ravnborg
2008-01-04 16:13   ` Sam Ravnborg [this message]
2008-01-04 17:26     ` [PATCH 1/3 v2] " Josh Boyer
2008-01-05 19:51       ` Sam Ravnborg
2008-01-03 22:04 ` [PATCH 2/3] Rework arch specific Makefiles to use mkubootimg Josh Boyer
2008-01-03 22:41   ` Ben Dooks
2008-01-03 22:58     ` Josh Boyer
2008-01-04  4:01       ` Paul Mundt
2008-01-04  9:19         ` Russell King
2008-01-04 10:33           ` Paul Mundt
2008-01-04 11:48             ` Josh Boyer
2008-01-04 12:07               ` Haavard Skinnemoen
2008-01-04 16:04               ` Russell King
2008-01-04 16:29                 ` Josh Boyer
2008-01-04  4:07       ` Bryan Wu
2008-01-03 22:05 ` [PATCH 3/3] Remove mkuboot.sh script Josh Boyer

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=20080104161336.GB31026@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=wd@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

all inboxes | Powered by JetHome®