From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: linux-next: Tree for Apr 1 (drivers/gpu/drm/i915)
Date: Tue, 01 Apr 2014 12:15:55 -0700 [thread overview]
Message-ID: <533B106B.8090408@infradead.org> (raw)
In-Reply-To: <20140401183907.a5127cadbe7116261096beaa@canb.auug.org.au>
On 04/01/2014 12:39 AM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add material intended for v3.16 to your linux-next included
> branches until after v3.15-rc1 is released.
>
> This tree still fails (more than usual) the powerpc allyesconfig build.
>
> Changes since 20140331:
>
for linux-next 0401 and 0331:
drivers/gpu/drm/i915/i915_cmd_parser.c:405:4: warning: format '%td' expects argument of type 'ptrdiff_t', but argument 5 has type 'long unsigned int' [-Wformat]
Just use %td without the (unsigned long) cast.
--
~Randy
next prev parent reply other threads:[~2014-04-01 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 7:39 linux-next: Tree for Apr 1 Stephen Rothwell
2014-04-01 18:34 ` linux-next: Tree for Apr 1 (netfilter) Randy Dunlap
2014-04-01 19:22 ` David Miller
2014-04-06 13:50 ` Geert Uytterhoeven
2014-04-06 15:31 ` David Miller
2014-04-06 16:08 ` Geert Uytterhoeven
2014-04-01 19:15 ` Randy Dunlap [this message]
2014-04-02 8:24 ` [PATCH] drm/i915: fix command parser debug print format mismatches Jani Nikula
2014-04-02 15:26 ` Randy Dunlap
2014-04-03 9:32 ` Daniel Vetter
2014-04-03 15:44 ` Damien Lespiau
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=533B106B.8090408@infradead.org \
--to=rdunlap@infradead.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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