From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Antti Palosaari" <crope@iki.fi>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: linux-media <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Brad Love <brad@nextdimension.cc>
Subject: Re: [PATCH v1] media: si2168: Refactor command setup code
Date: Wed, 3 Jul 2019 16:15:35 +0200 [thread overview]
Message-ID: <68ae0fde-ce8b-968d-853f-86eb5b1247aa@free.fr> (raw)
In-Reply-To: <6a644c94-f979-b656-472b-c7fe9303e08c@free.fr>
On 03/07/2019 14:47, Marc Gonzalez wrote:
> Come to think of it, I'm really not a fan of "large" macro functions.
> I'll outline a different option in v2.
My idea is to use a trivial helper function to assign the 3 struct fields,
and then a trivial macro to invoke the helper:
static void cmd_setup(struct si2168_cmd *cmd, char *args, int wlen, int rlen)
{
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)
I think this way addresses all of your comments:
- since we're using a real function, the compiler can perform type-checking,
and the function's prototype is self-documenting.
- no more funky __args and __rlen arguments
- no local variables
Note however, that drivers/media/tuners/si2157.c uses a different struct
(struct si2157_cmd). Therefore, if we wanted to apply the same changes
to si2157.c, we would have to define a common struct, and replace all
the uses of struct si2157_cmd and struct si2168_cmd. That seemed too
invasive to do without the maintainer's approval and guidance.
Antti, do you Ack this new approach?
It's not clear what HW is supported by drivers/media/dvb-frontends/si21xx.c
(that's a very generic name).
Regards.
next prev parent reply other threads:[~2019-07-03 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 11:44 [PATCH v1] media: si2168: Refactor command setup code Marc Gonzalez
2019-07-02 8:37 ` Marc Gonzalez
2019-07-02 9:51 ` Jonathan Neuschäfer
2019-07-03 12:47 ` Marc Gonzalez
2019-07-03 14:15 ` Marc Gonzalez [this message]
2019-07-03 16:35 ` Jonathan Neuschäfer
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=68ae0fde-ce8b-968d-853f-86eb5b1247aa@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-kernel@vger.kernel.org \
--cc=linux-media@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).