* [PATCH 3/3] i2c: i2c-core: fix coding style issues in i2c-core.c
@ 2013-10-14 15:25 RAGHAVENDRA GANIGA
[not found] ` <525C0CDB.6020305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: RAGHAVENDRA GANIGA @ 2013-10-14 15:25 UTC (permalink / raw)
To: wsa; +Cc: linux-i2c, linux-kernel, ravi23ganiga
>From 2c324e677fd8bfb0ad13a8c949317e40cc5fd23e Mon Sep 17 00:00:00 2001
From: Raghavendra Ganiga <ravi23ganiga@gmail.com>
Date: Mon, 14 Oct 2013 20:42:37 +0530
Subject: [PATCH 3/3] i2c: i2c-core: fix coding style issues in i2c-core.c
This is a patch to the i2c-core.c file that fixes the
coding style issues found by checkpatch.pl tool
Signed-off-by: Raghavendra Chandra Ganiga <ravi23ganiga@gmail.com>
---
drivers/i2c/i2c-core.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
index 66e38a9..7e95fcd 100644
--- a/drivers/i2c/i2c-core.c
+++ b/drivers/i2c/i2c-core.c
@@ -1737,9 +1737,9 @@ int i2c_transfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
for (ret = 0; ret < num; ret++) {
dev_dbg(&adap->dev, "master_xfer[%d] %c, addr=0x%02x, len=%d%s\n",
ret,
- ((msgs[ret].flags & I2C_M_RD) ? 'R' : 'W'),
+ msgs[ret].flags & I2C_M_RD ? 'R' : 'W',
msgs[ret].addr, msgs[ret].len,
- (msgs[ret].flags & I2C_M_RECV_LEN) ? "+" : "");
+ msgs[ret].flags & I2C_M_RECV_LEN ? "+" : "");
}
#endif
@@ -2120,7 +2120,8 @@ EXPORT_SYMBOL(i2c_smbus_read_byte);
s32 i2c_smbus_write_byte(const struct i2c_client *client, u8 value)
{
return i2c_smbus_xfer(client->adapter, client->addr, client->flags,
- I2C_SMBUS_WRITE, value, I2C_SMBUS_BYTE, NULL);
+ I2C_SMBUS_WRITE, value,
+ I2C_SMBUS_BYTE, NULL);
}
EXPORT_SYMBOL(i2c_smbus_write_byte);
--
1.7.10.4
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 3/3] i2c: i2c-core: fix coding style issues in i2c-core.c
[not found] ` <525C0CDB.6020305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2014-01-14 18:38 ` Wolfram Sang
2014-01-14 19:06 ` Joe Perches
0 siblings, 1 reply; 3+ messages in thread
From: Wolfram Sang @ 2014-01-14 18:38 UTC (permalink / raw)
To: RAGHAVENDRA GANIGA
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -1737,9 +1737,9 @@ int i2c_transfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
> for (ret = 0; ret < num; ret++) {
> dev_dbg(&adap->dev, "master_xfer[%d] %c, addr=0x%02x, len=%d%s\n",
> ret,
> - ((msgs[ret].flags & I2C_M_RD) ? 'R' : 'W'),
> + msgs[ret].flags & I2C_M_RD ? 'R' : 'W',
> msgs[ret].addr, msgs[ret].len,
> - (msgs[ret].flags & I2C_M_RECV_LEN) ? "+" : "");
> + msgs[ret].flags & I2C_M_RECV_LEN ? "+" : "");
Don't spend time changing too much here like the paranthesis. It will
probably be removed soon in favour of the tracing approach.
> @@ -2120,7 +2120,8 @@ EXPORT_SYMBOL(i2c_smbus_read_byte);
> s32 i2c_smbus_write_byte(const struct i2c_client *client, u8 value)
> {
> return i2c_smbus_xfer(client->adapter, client->addr, client->flags,
> - I2C_SMBUS_WRITE, value, I2C_SMBUS_BYTE, NULL);
> + I2C_SMBUS_WRITE, value,
> + I2C_SMBUS_BYTE, NULL);
Not worth the change IMO. Just drop this patch.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 3/3] i2c: i2c-core: fix coding style issues in i2c-core.c
2014-01-14 18:38 ` Wolfram Sang
@ 2014-01-14 19:06 ` Joe Perches
0 siblings, 0 replies; 3+ messages in thread
From: Joe Perches @ 2014-01-14 19:06 UTC (permalink / raw)
To: Wolfram Sang; +Cc: RAGHAVENDRA GANIGA, linux-i2c, linux-kernel
On Tue, 2014-01-14 at 19:38 +0100, Wolfram Sang wrote:
> > --- a/drivers/i2c/i2c-core.c
> > +++ b/drivers/i2c/i2c-core.c
> > @@ -1737,9 +1737,9 @@ int i2c_transfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
> > for (ret = 0; ret < num; ret++) {
> > dev_dbg(&adap->dev, "master_xfer[%d] %c, addr=0x%02x, len=%d%s\n",
> > ret,
> > - ((msgs[ret].flags & I2C_M_RD) ? 'R' : 'W'),
> > + msgs[ret].flags & I2C_M_RD ? 'R' : 'W',
> > msgs[ret].addr, msgs[ret].len,
> > - (msgs[ret].flags & I2C_M_RECV_LEN) ? "+" : "");
> > + msgs[ret].flags & I2C_M_RECV_LEN ? "+" : "");
>
> Don't spend time changing too much here like the paranthesis. It will
> probably be removed soon in favour of the tracing approach.
That'd be good. There are a lot of function tracing style
dev_dbg uses in i2c-core that can be removed.
Just an fyi not to Raghavendra:
This sort of loop could have been further modified removing
the unnecessary #if DEBUG/#endif too
Also, reusing ret for a loop index is efficient, but a bit odd.
Maybe something like:
diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
index d74c0b3..5ca078e 100644
--- a/drivers/i2c/i2c-core.c
+++ b/drivers/i2c/i2c-core.c
@@ -1758,14 +1758,13 @@ int i2c_transfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
*/
if (adap->algo->master_xfer) {
-#ifdef DEBUG
- for (ret = 0; ret < num; ret++) {
- dev_dbg(&adap->dev, "master_xfer[%d] %c, addr=0x%02x, "
- "len=%d%s\n", ret, (msgs[ret].flags & I2C_M_RD)
- ? 'R' : 'W', msgs[ret].addr, msgs[ret].len,
- (msgs[ret].flags & I2C_M_RECV_LEN) ? "+" : "");
- }
-#endif
+ int i;
+
+ for (i = 0; i < num; i++)
+ dev_dbg(&adap->dev, "master_xfer[%d] %c, addr=0x%02x, len=%d%s\n",
+ ret, msgs[i].flags & I2C_M_RD ? 'R' : 'W',
+ msgs[i].addr, msgs[i].len,
+ msgs[i].flags & I2C_M_RECV_LEN ? "+" : "");
if (in_atomic() || irqs_disabled()) {
ret = i2c_trylock_adapter(adap);
^ permalink raw reply related [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-01-14 19:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-14 15:25 [PATCH 3/3] i2c: i2c-core: fix coding style issues in i2c-core.c RAGHAVENDRA GANIGA
[not found] ` <525C0CDB.6020305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-14 18:38 ` Wolfram Sang
2014-01-14 19:06 ` Joe Perches
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).