From: Tomasz Figa <tomasz.figa@gmail.com>
To: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] exynos: fix G2D_DOUBLE_TO_FIXED
Date: Sun, 01 Jun 2014 02:48:18 +0200 [thread overview]
Message-ID: <538A7852.8080403@gmail.com> (raw)
In-Reply-To: <1401400700-3725-2-git-send-email-tjakobi@math.uni-bielefeld.de>
Hi Tobias,
First of all, thanks for spotting those issues and sending patches.
However looking at libdrm repo history, your patches don't seem to
follow formatting guidelines used there: they lack commit messages
(which should say what is changed and why) and your signed-off-by tags.
Also it is usually a good idea to include respective maintainers on Cc
list, although unfortunately I'm not sure who would that be in case of
libdrm.
One more comment inline.
On 29.05.2014 23:58, Tobias Jakobi wrote:
> ---
> exynos/fimg2d.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/exynos/fimg2d.h b/exynos/fimg2d.h
> index 1aac378..bc45ab5 100644
> --- a/exynos/fimg2d.h
> +++ b/exynos/fimg2d.h
> @@ -25,7 +25,7 @@
> #define G2D_MAX_CMD_LIST_NR 64
> #define G2D_PLANE_MAX_NR 2
>
> -#define G2D_DOUBLE_TO_FIXED(d) ((unsigned int)(d) * 65536.0)
> +#define G2D_DOUBLE_TO_FIXED(d) ((unsigned int)(d * 65536.0))
You should also keep the parentheses around d, so that the macro
evaluates correctly even if an expression is passed as the argument.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-06-01 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 21:58 [PATCH 1/3] exynos: fix g2d_copy Tobias Jakobi
2014-05-29 21:58 ` [PATCH 2/3] exynos: fix G2D_DOUBLE_TO_FIXED Tobias Jakobi
2014-06-01 0:48 ` Tomasz Figa [this message]
2014-06-01 1:14 ` Tobias Jakobi
2014-06-01 1:49 ` Tomasz Figa
2014-05-29 21:58 ` [PATCH 3/3] exynos: fix g2d_copy_with_scale Tobias Jakobi
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=538A7852.8080403@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tjakobi@math.uni-bielefeld.de \
/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.