From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 2/2] mkimage: Refactor mxsimage to use common crc32 code
Date: Tue, 13 May 2014 17:08:40 -0400 [thread overview]
Message-ID: <20140513210840.GS22182@bill-the-cat> (raw)
In-Reply-To: <201405131927.18641.manningc2@actrix.gen.nz>
On Tue, May 13, 2014 at 07:27:18PM +1200, Charles Manning wrote:
> On Tuesday 13 May 2014 08:26:44 Tom Rini wrote:
> > On Tue, May 06, 2014 at 10:46:46AM +1200, Charles Manning wrote:
> > > mxsimage uses the same crc32 function as pblimage.
> > >
> > > Signed-off-by: Charles Manning <cdhmanning@gmail.com>
> > > Acked-by: Stefano Babic <sbabic@denx.de>
> >
> > This introduces warnings:
> > tools/mxsimage.c: In function ?sb_build_command_load?:
> > tools/mxsimage.c:979:2: warning: pointer targets in passing argument 2 of
> > ?pbl_crc32? differ in signedness [-Wpointer-sign] tools/pbl_crc32.h:11:10:
> > note: expected ?const char *? but argument is of type ?uint8_t *?
> > u-boot/tools/mxsimage.c: In function ?sb_verify_command?:
> > tools/mxsimage.c:1815:3: warning: pointer targets in passing argument 2 of
> > ?pbl_crc32? differ in signedness [-Wpointer-sign] tools/pbl_crc32.h:11:10:
> > note: expected ?const char *? but argument is of type ?uint8_t *?
>
> Thanks for the feedback.
>
> Will it be acceptable to do the following:
>
> *Change the called function from uint8_t * to const uint8_t
> *Cast the const char * pointer to const uint8_t *.
Sounds right.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140513/5dfa0834/attachment.pgp>
next prev parent reply other threads:[~2014-05-13 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 22:46 [U-Boot] [PATCH 0/2] mkimage: Refactor and clean up 32-bit crcs Charles Manning
2014-05-05 22:46 ` [U-Boot] [PATCH 1/2] mkimage : Split out and clean pbl_crc32 for use by other image types Charles Manning
2014-05-06 8:10 ` Stefano Babic
2014-05-05 22:46 ` [U-Boot] [PATCH 2/2] mkimage: Refactor mxsimage to use common crc32 code Charles Manning
2014-05-06 8:11 ` Stefano Babic
2014-05-12 20:26 ` [U-Boot] [U-Boot, " Tom Rini
2014-05-13 7:27 ` Charles Manning
2014-05-13 21:08 ` Tom Rini [this message]
2014-05-14 2:44 ` [U-Boot] [PATCH v2 0/2] mkimage: Refactor and clean up 32-bit crcs Charles Manning
2014-05-14 2:45 ` [U-Boot] [PATCH v2 1/2] mkimage : Split out and clean pbl_crc32 for use by other image types Charles Manning
2014-06-05 22:46 ` [U-Boot] [U-Boot, v2, " Tom Rini
2014-05-14 2:45 ` [U-Boot] [PATCH v2 2/2] tools: Refactor mxsimage to use pbl_crc32 Charles Manning
2014-06-05 22:46 ` [U-Boot] [U-Boot, v2, " Tom Rini
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=20140513210840.GS22182@bill-the-cat \
--to=trini@ti.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