linux-kernel - Re: [PATCH 1/7] remoteproc: fix print format warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK=WgbbCYmGDATEG-cQFphcvhjZszpW7=mD3qd6q4VN-gZusDg@mail.gmail.com>
Date:	Sun, 10 Jun 2012 15:04:47 +0300
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	sjur.brandeland@...ricsson.com
Cc:	Loic PALLARDY <loic.pallardy@...ricsson.com>,
	Ludovic BARRE <ludovic.barre@...ricsson.com>,
	linux-kernel@...r.kernel.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Sjur Brændeland <sjurbren@...il.com>
Subject: Re: [PATCH 1/7] remoteproc: fix print format warnings

On Wed, Jun 6, 2012 at 4:38 PM, <sjur.brandeland@...ricsson.com> wrote:
> From: Sjur Brændeland <sjur.brandeland@...ricsson.com>
>
> Fix compile warnings from GCC 4.6.1 when printing values of type size_t.
>
> drivers/remoteproc/remoteproc_core.c:251:6:
> warning: format ‘%x’ expects argument of type ‘unsigned int’,
> but argument 4 has type ‘size_t’ [-Wformat]
> drivers/remoteproc/remoteproc_core.c:938:9:
> warning: format ‘%u’ expects argument of type ‘unsigned int’,
> but argument 4 has type ‘size_t’ [-Wformat]
> drivers/remoteproc/remoteproc_core.c:1023:2:
> warning: format ‘%d’ expects argument of type ‘int’,
> but argument 4 has type ‘size_t’ [-Wformat]
>
> Signed-off-by: Sjur Brændeland <sjur.brandeland@...ricsson.com>

Cc'ed stable, applied and pushed to remoteproc's fixes branch.

Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/