From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [media-s3c-camif] question about arguments position
Date: Thu, 4 May 2017 21:34:47 +0200 [thread overview]
Message-ID: <e2137221-f094-530b-e61c-70e28f22a83f@gmail.com> (raw)
In-Reply-To: <20170504140502.Horde.e_TqvS0_CEqTDsNh1soDOGo@gator4166.hostgator.com>
Hi Gustavo,
On 05/04/2017 09:05 PM, Gustavo A. R. Silva wrote:
> The issue here is that the position of arguments in the call to
> camif_hw_set_effect() function do not match the order of the parameters:
>
> camif->colorfx_cb is passed to cr
> camif->colorfx_cr is passed to cb
>
> This is the function prototype:
>
> void camif_hw_set_effect(struct camif_dev *camif, unsigned int effect,
> unsigned int cr, unsigned int cb)
>
> My question here is if this is intentional?
>
> In case it is not, I will send a patch to fix it. But first it would be
> great to hear any comment about it.
You are right, it seems you have found a real bug. Feel free to send a patch.
The best thing to do now might be to change the function prototype to:
void camif_hw_set_effect(struct camif_dev *camif, unsigned int effect,
unsigned int cb, unsigned int cr)
--
Regards,
Sylwester
next prev parent reply other threads:[~2017-05-04 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 19:05 [media-s3c-camif] question about arguments position Gustavo A. R. Silva
2017-05-04 19:34 ` Sylwester Nawrocki [this message]
2017-05-04 19:50 ` Gustavo A. R. Silva
2017-05-04 21:42 ` [PATCH] media: platform: s3c-camif: fix function prototype Gustavo A. R. Silva
2017-05-22 9:02 ` Hans Verkuil
2017-06-01 21:37 ` Sylwester Nawrocki
2017-06-02 3:43 ` [PATCH] media: platform: s3c-camif: fix arguments position in function call Gustavo A. R. Silva
2017-06-05 10:07 ` Sylwester Nawrocki
2017-06-05 15:52 ` Gustavo A. R. Silva
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=e2137221-f094-530b-e61c-70e28f22a83f@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=garsilva@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).