From: Thierry Reding <thierry.reding@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "Terje Bergström" <tbergstrom@nvidia.com>,
"David Airlie" <airlied@linux.ie>,
"Stephen Warren" <swarren@wwwdotorg.org>,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch 2/2] drm/tegra: silence some sparse complaints
Date: Fri, 08 Nov 2013 12:34:56 +0000 [thread overview]
Message-ID: <20131108123455.GA31551@ulmo.nvidia.com> (raw)
In-Reply-To: <20131108100803.GY27977@elgon.mountain>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Fri, Nov 08, 2013 at 01:08:03PM +0300, Dan Carpenter wrote:
> I've shifted the __user markup to make Sparse happy.
>
> drivers/gpu/drm/tegra/drm.c:138:18: warning: incorrect type in initializer (different address spaces)
> drivers/gpu/drm/tegra/drm.c:138:18: expected struct drm_tegra_cmdbuf [noderef] <asn:1>*cmdbufs
> drivers/gpu/drm/tegra/drm.c:138:18: got void *[noderef] <asn:1><noident>
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Hi Dan,
I fixed exactly the same sparse warnings (along with many others this
morning). We really ought to have a tag to put into a commit to credit
people who've come up with the same patch at the same time.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "Terje Bergström" <tbergstrom@nvidia.com>,
"David Airlie" <airlied@linux.ie>,
"Stephen Warren" <swarren@wwwdotorg.org>,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch 2/2] drm/tegra: silence some sparse complaints
Date: Fri, 8 Nov 2013 13:34:56 +0100 [thread overview]
Message-ID: <20131108123455.GA31551@ulmo.nvidia.com> (raw)
In-Reply-To: <20131108100803.GY27977@elgon.mountain>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Fri, Nov 08, 2013 at 01:08:03PM +0300, Dan Carpenter wrote:
> I've shifted the __user markup to make Sparse happy.
>
> drivers/gpu/drm/tegra/drm.c:138:18: warning: incorrect type in initializer (different address spaces)
> drivers/gpu/drm/tegra/drm.c:138:18: expected struct drm_tegra_cmdbuf [noderef] <asn:1>*cmdbufs
> drivers/gpu/drm/tegra/drm.c:138:18: got void *[noderef] <asn:1><noident>
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Hi Dan,
I fixed exactly the same sparse warnings (along with many others this
morning). We really ought to have a tag to put into a commit to credit
people who've come up with the same patch at the same time.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-08 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 10:08 [patch 2/2] drm/tegra: silence some sparse complaints Dan Carpenter
2013-11-08 10:08 ` Dan Carpenter
2013-11-08 12:34 ` Thierry Reding [this message]
2013-11-08 12:34 ` Thierry Reding
[not found] ` <20131108123455.GA31551-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2013-11-08 13:29 ` Dan Carpenter
2013-11-08 13:29 ` Dan Carpenter
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=20131108123455.GA31551@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=tbergstrom@nvidia.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 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.