From: Julia Lawall <julia.lawall@lip6.fr>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Shubhrajyoti <shubhrajyoti@ti.com>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
julia.lawall@lip6.fr
Subject: Re: [PATCH 3/7] rtc: Convert struct i2c_msg initialization to C99 format
Date: Tue, 18 Sep 2012 07:53:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1209180752080.2056@localhost6.localdomain6> (raw)
In-Reply-To: <50580AF1.4060109@gmail.com>
On Tue, 18 Sep 2012, Ryan Mallon wrote:
> On 18/09/12 15:40, Shubhrajyoti wrote:
>> On Tuesday 18 September 2012 07:21 AM, Ryan Mallon wrote:
>>> Actually, I wonder if it is useful to have something like:.
>> Read and write differ only in the flag also it will be a deviation from
>> what $SUBJECT
>> would warrant. So could be a separate patch.
>
> Sure, but I think it would help make the code even more readable than
> just converting to C99 initialisers (especially since putting the C99
> initialiser all on one line is hard to read),
The one line thing is the fault of Coccinelle :)
julia
> and there is little sense
> in doing one clean up and then replacing it later with a different clean up.
>
> If you are worried about the duplication of code for a single flag
> difference you could always do:
>
> #define I2C_OP(_addr, _buf, _len, _flags) \
> ...
>
> #define I2C_WRITE(addr, buf, len) I2C_OP(addr, buf, len, 0)
> #define I2C_READ(addr, buf, len) I2C_OP(addr, buf, len, I2C_M_RD)
>
> ~Ryan
>
>>>
>>> #define I2C_WRITE(_addr, _buf, _len) { \
>>> .addr = _addr, \
>>> .buf = _buf, \
>>> .len = _len, \
>>> }
>>>
>>> #define I2C_READ(_addr, _buf, _len) { \
>>> .addr = _addr, \
>>> .buf = _buf, \
>>> .len = _len, \
>>> .flags = I2C_M_RD, \
>>> }
>>>
>>> and then write this as:
>>>
>>> struct i2c_msg msgs[2] = {
>>> I2C_WRITE(client->addr, reg_addr, sizeof(reg_addr)),
>>> I2C_READ(client->addr, buf, len),
>>> };
>>
>
>
next prev parent reply other threads:[~2012-09-18 5:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 13:58 [PATCH 0/7] rtc: convert to c99 format Shubhrajyoti D
2012-09-17 13:58 ` [PATCH 1/7] rtc: Convert struct i2c_msg initialization to C99 format Shubhrajyoti D
2012-09-18 1:44 ` Ryan Mallon
2012-09-18 6:05 ` Shubhrajyoti
2012-09-18 6:10 ` Ryan Mallon
2012-09-17 13:58 ` [PATCH 2/7] " Shubhrajyoti D
2012-09-17 13:58 ` [PATCH 3/7] " Shubhrajyoti D
2012-09-18 1:45 ` Ryan Mallon
2012-09-18 5:38 ` Shubhrajyoti
2012-09-18 1:51 ` Ryan Mallon
2012-09-18 5:40 ` Shubhrajyoti
2012-09-18 5:47 ` Ryan Mallon
2012-09-18 5:53 ` Julia Lawall [this message]
2012-09-17 13:58 ` [PATCH 4/7] " Shubhrajyoti D
2012-09-17 13:58 ` [PATCH 5/7] " Shubhrajyoti D
2012-09-17 13:58 ` [PATCH 6/7] " Shubhrajyoti D
2012-09-17 13:58 ` [PATCH 7/7] " Shubhrajyoti D
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=alpine.DEB.2.02.1209180752080.2056@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rmallon@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=shubhrajyoti@ti.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®