From: Ryan Mallon <rmallon@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/3] include/linux/i2c.h: introduce macros for i2c_msg initialization
Date: Mon, 01 Oct 2012 22:24:49 +0000 [thread overview]
Message-ID: <506A1831.6020101@gmail.com> (raw)
In-Reply-To: <1348990388-7413-3-git-send-email-Julia.Lawall@lip6.fr>
On 30/09/12 17:33, Julia Lawall wrote:
> From: Julia Lawall <Julia.Lawall@lip6.fr>
>
> This patch introduces some macros for describing how an i2c_msg is being
> initialized. There are three macros: I2C_MSG_READ, for a read message,
> I2C_MSG_WRITE, for a write message, and I2C_MSG_OP, for some other kind of
> message, which is expected to be very rarely used.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Looks good to me. You can add:
Reviewed-by: Ryan Mallon <rmallon@gmail.com>
>
> ---
> include/linux/i2c.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/linux/i2c.h b/include/linux/i2c.h
> index 5970266..0990071 100644
> --- a/include/linux/i2c.h
> +++ b/include/linux/i2c.h
> @@ -556,6 +556,13 @@ struct i2c_msg {
> __u8 *buf; /* pointer to msg data */
> };
>
> +#define I2C_MSG_OP(_addr, _buf, _len, _flags) \
> + { .addr = _addr, .buf = _buf, .len = _len, .flags = _flags }
> +
> +#define I2C_MSG_WRITE(addr, buf, len) I2C_MSG_OP(addr, buf, len, 0)
> +#define I2C_MSG_READ(addr, buf, len) I2C_MSG_OP(addr, buf, len, I2C_M_RD)
> +
> +
> /* To determine what functionality is present */
>
> #define I2C_FUNC_I2C 0x00000001
>
next prev parent reply other threads:[~2012-10-01 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 7:33 [PATCH 1/3] include/linux/i2c.h: introduce macros for i2c_msg initialization Julia Lawall
2012-10-01 22:24 ` Ryan Mallon [this message]
2012-10-01 22:47 ` Peter Hüwe
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=506A1831.6020101@gmail.com \
--to=rmallon@gmail.com \
--cc=kernel-janitors@vger.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 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.