From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: linux-next: Tree for Jun 5 (mmc/host/usdhi6ro10.c)
Date: Thu, 05 Jun 2014 10:07:24 -0700 [thread overview]
Message-ID: <5390A3CC.2020309@infradead.org> (raw)
In-Reply-To: <20140605192853.0344d9d3@canb.auug.org.au>
On 06/05/2014 02:28 AM, Stephen Rothwell wrote:
> Hi all,
>
> The powerpc allyesconfig is again broken more than usual.
>
> Our build server is down today, so this linux-next will not get the
> usual builds done, sorry.
>
> Changes since 20140604:
>
>
> The mmc tree lost its build failure.
but has a bunch of printk format warnings on x86_64:
../drivers/mmc/host/usdhi6rol0.c:359:2: warning: format '%zd' expects argument of type 'signed size_t', but argument 4 has type 'unsigned int' [-Wformat]
../drivers/mmc/host/usdhi6rol0.c:359:2: warning: format '%zd' expects argument of type 'signed size_t', but argument 5 has type 'unsigned int' [-Wformat]
../drivers/mmc/host/usdhi6rol0.c:462:2: warning: format '%u' expects argument of type 'unsigned int', but argument 7 has type 'size_t' [-Wformat]
../drivers/mmc/host/usdhi6rol0.c:491:3: warning: format '%zd' expects argument of type 'signed size_t', but argument 4 has type 'unsigned int' [-Wformat]
../drivers/mmc/host/usdhi6rol0.c:491:3: warning: format '%zd' expects argument of type 'signed size_t', but argument 5 has type 'unsigned int' [-Wformat]
../drivers/mmc/host/usdhi6rol0.c:898:2: warning: format '%x' expects argument of type 'unsigned int', but argument 9 has type 'size_t' [-Wformat]
../drivers/mmc/host/usdhi6rol0.c:1668:3: warning: format '%x' expects argument of type 'unsigned int', but argument 6 has type 'size_t' [-Wformat]
--
~Randy
prev parent reply other threads:[~2014-06-05 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 9:28 linux-next: Tree for Jun 5 Stephen Rothwell
2014-06-05 17:07 ` Randy Dunlap [this message]
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=5390A3CC.2020309@infradead.org \
--to=rdunlap@infradead.org \
--cc=chris@printf.net \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ulf.hansson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.