From: Paul Bolle <pebolle@tiscali.nl>
To: VMware Graphics <linux-graphics-maintainer@vmware.com>,
Sinclair Yeh <syeh@vmware.com>,
Thomas Hellstrom <thellstrom@vmware.com>
Cc: Joe Perches <joe@perches.com>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/vmwgfx: use *_32_bits() macros
Date: Wed, 15 Jun 2016 10:37:24 +0200 [thread overview]
Message-ID: <1465979844.9515.11.camel@tiscali.nl> (raw)
In-Reply-To: <1460644444.19090.17.camel@perches.com>
[Added Sinclair, Thomas, and "VMware Graphics".]
On do, 2016-04-14 at 07:34 -0700, Joe Perches wrote:
> On Thu, 2016-04-14 at 13:32 +0200, Paul Bolle wrote:
> > On do, 2016-03-03 at 11:26 +0100, Paul Bolle wrote:
> > >
> > > Use the upper_32_bits() macro instead of the four line equivalent that
> > > triggers a GCC warning on 32 bits x86:
> > > drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c: In function
> > > 'vmw_cmdbuf_header_submit':
> > > drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c:297:25: warning: right
> > > shift count >= width of type [-Wshift-count-overflow]
> > > val = (header->handle >> 32);
> > > ^
> > >
> > > And use the lower_32_bits() macro instead of and-ing with a 32 bits
> > > mask.
> > >
> > > Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> > > ---
> > > Note: compile tested only (I don't use any of vmware's products).
> > The warning can still be seen on v4.6-rc3 for 32 bits x86. This patch
> > applies cleanly to that rc.
> >
> > Has anyone had a chance to look at this patch, and perhaps even test
> > it?
>
> Test? Nope. Seems obviously correct.
This warning still shows up when building v4.7-rc3 for 32 bits x86.
Since my previous message an entry for this driver showed up in
MAINTAINERS. So I'd guess Sinclair, Thomas, etc want me to resend this
small patch. Is that correct?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2016-06-15 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 10:26 Paul Bolle
2016-04-14 11:32 ` Paul Bolle
2016-04-14 14:34 ` Joe Perches
2016-06-15 8:37 ` Paul Bolle [this message]
2016-06-15 11:11 ` Daniel Vetter
2016-06-15 11:59 ` Thomas Hellstrom
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=1465979844.9515.11.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syeh@vmware.com \
--cc=thellstrom@vmware.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
Powered by JetHome