From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Antti Palosaari" <crope@iki.fi>,
"Brad Love" <brad@nextdimension.cc>, "Sean Young" <sean@mess.org>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-media <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v3] media: si2168: Refactor command setup code
Date: Fri, 12 Jul 2019 11:37:42 +0200 [thread overview]
Message-ID: <b84104ca-6e4e-24ee-91e0-56aebd036a48@free.fr> (raw)
In-Reply-To: <20190712084343.GA28962@taurus.defre.kleine-koenig.org>
+ Sean
On 12/07/2019 10:43, Uwe Kleine-König wrote:
> On Thu, Jul 04, 2019 at 12:33:22PM +0200, Marc Gonzalez wrote:
>
>> Refactor the command setup code, and let the compiler determine
>> the size of each command.
>>
>> Reviewed-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
>> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
>> ---
>> Changes from v1:
>> - Use a real function to populate struct si2168_cmd *cmd, and a trivial
>> macro wrapping it (macro because sizeof).
>> Changes from v2:
>> - Fix header mess
>> - Add Jonathan's tag
>> ---
>> drivers/media/dvb-frontends/si2168.c | 146 +++++++++------------------
>> 1 file changed, 45 insertions(+), 101 deletions(-)
>>
>> diff --git a/drivers/media/dvb-frontends/si2168.c b/drivers/media/dvb-frontends/si2168.c
>> index c64b360ce6b5..5e81e076369c 100644
>> --- a/drivers/media/dvb-frontends/si2168.c
>> +++ b/drivers/media/dvb-frontends/si2168.c
>> @@ -12,6 +12,16 @@
>>
>> static const struct dvb_frontend_ops si2168_ops;
>>
>> +static void cmd_setup(struct si2168_cmd *cmd, char *args, int wlen, int rlen)
>
> I'd add an "inline" here. And you could add a const for *args.
I was under the (vague) impression that it's better to let the compiler
decide when to inline, except for trivial alternatives in headers.
David Miller wrote: "Please do not use the inline directive in foo.c
files, let the compiler decide."
Antti, Sean, what do you think?
For my notes: https://gcc.gnu.org/onlinedocs/gcc/Inline.html
>> +{
>> + memcpy(cmd->args, args, wlen);
>> + cmd->wlen = wlen;
>> + cmd->rlen = rlen;
>> +}
>> +
>> +#define CMD_SETUP(cmd, args, rlen) \
>> + cmd_setup(cmd, args, sizeof(args) - 1, rlen)
>
> Here is the chance to add some static checking. Also it is a good habit
> to put parens around macro arguments.
Wrt parens around arguments, I figured they are not required here, since they
are used as function arguments. Though you may have a valid point.
Antti, Sean?
> Something like:
>
> #define CMD_SETUP(cmd, args, rlen) ({ \
> BUILD_BUG_ON(sizeof((args)) - 1 > SI2168_ARGLEN);
> cmd_setup((cmd), (args), __must_be_array((args)) + sizeof((args)) - 1, (rlen));
>
> Maybe let this macro live in drivers/media/dvb-frontends/si2168_priv.h
> where struct si2168_cmd is defined?
Antti, Sean?
> I looked over the transformations in the rest of the patch and this
> looks good.
Thanks for taking a look!
Regards.
next prev parent reply other threads:[~2019-07-12 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 10:33 Marc Gonzalez
2019-07-12 8:43 ` Uwe Kleine-König
2019-07-12 9:37 ` Marc Gonzalez [this message]
2019-07-12 15:47 ` Brad Love
2019-07-12 17:45 ` Mauro Carvalho Chehab
2019-07-12 22:11 ` Marc Gonzalez
2019-07-13 10:02 ` Mauro Carvalho Chehab
2019-07-14 18:31 ` Matthias Schwarzott
2019-07-12 21:41 ` Marc Gonzalez
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=b84104ca-6e4e-24ee-91e0-56aebd036a48@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=bjorn.andersson@linaro.org \
--cc=brad@nextdimension.cc \
--cc=crope@iki.fi \
--cc=j.neuschaefer@gmx.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sean@mess.org \
--cc=uwe@kleine-koenig.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
all inboxes | Powered by JetHome®