From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Rob Clark <robdclark@gmail.com>, Dave Airlie <airlied@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Luis de Bethencourt <luisbg@osg.samsung.com>,
<linux-omap@vger.kernel.org>, <linux-fbdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] omapfb/dss: wait_for_completion_interruptible_timeout expects long
Date: Wed, 10 Aug 2016 13:21:46 +0300 [thread overview]
Message-ID: <cff34342-3574-d197-df08-dc5b9b6ced80@ti.com> (raw)
In-Reply-To: <1469466767-23352-1-git-send-email-hofrat@osadl.org>
[-- Attachment #1.1: Type: text/plain, Size: 1087 bytes --]
On 25/07/16 20:12, Nicholas Mc Guire wrote:
> wait_for_completion_timeout_interruptible returns long not unsigned long.
> an appropriately typed variable is introduced and assignments fixed up.
>
> Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
> ---
>
> API non-compliance was located by coccinelle
>
> This is mostly cosmetic since the returned value is only compared
> at present, however if remaining time (completion occurred) where ever
> used, then a signal received would be interpreted as a large remaining
> jiffies left, which would be wrong.
>
> Compile tested with: omap2plus_defconfig (implies CONFIG_FB_OMAP2_DSS)
>
> Patch is against 4.7.0-rc7 (localversion-next -next-20160724)
>
> drivers/video/fbdev/omap2/omapfb/dss/dispc-compat.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Thanks, queued for v4.9. I dropped the "Fixes: " line, as that commit
only does a copy of the files, so the commit didn't really introduce the
bug.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-10 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:12 Nicholas Mc Guire
2016-08-10 10:21 ` Tomi Valkeinen [this message]
2016-08-10 10:30 ` Nicholas Mc Guire
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=cff34342-3574-d197-df08-dc5b9b6ced80@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@gmail.com \
--cc=hofrat@osadl.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=peter.ujfalusi@ti.com \
--cc=plagnioj@jcrosoft.com \
--cc=robdclark@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
all inboxes | Powered by JetHome®