From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Fix build warning on 32-bit
Date: Wed, 26 Aug 2015 09:39:30 +0200 [thread overview]
Message-ID: <20150826073930.GS20434@phenom.ffwll.local> (raw)
In-Reply-To: <87si768q8k.fsf@intel.com>
On Wed, Aug 26, 2015 at 10:26:35AM +0300, Jani Nikula wrote:
> On Wed, 26 Aug 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Mon, Aug 17, 2015 at 05:19:09PM +0000, Zanoni, Paulo R wrote:
> >> Em Sex, 2015-08-14 às 12:35 +0200, Thierry Reding escreveu:
> >> > From: Thierry Reding <treding@nvidia.com>
> >> >
> >> > The gtt.stolen_size field is of type size_t, and so should be printed
> >> > using %zu to avoid build warnings on either 32-bit and 64-bit builds.
> >>
> >> While the suggestion from Chris sounds good, this patch alone is
> >> already a fix, so:
> >> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
> > Queued for -next, thanks for the patch.
>
> Great. Also pushed to drm-intel-next-fixes.
Oops, dropped again from dinq ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-08-26 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 10:35 [PATCH] drm/i915: Fix build warning on 32-bit Thierry Reding
2015-08-14 11:04 ` [Intel-gfx] " Chris Wilson
2015-08-17 17:19 ` Zanoni, Paulo R
2015-08-26 7:11 ` [Intel-gfx] " Daniel Vetter
2015-08-26 7:26 ` Jani Nikula
2015-08-26 7:39 ` Daniel Vetter [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=20150826073930.GS20434@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=thierry.reding@gmail.com \
/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