The patch titled Subject: drivers/rtc/rtc-s35390a.c: convert struct i2c_msg initialization to C99 format has been removed from the -mm tree. Its filename was drivers-rtc-rtc-s35390ac-convert-struct-i2c_msg-initialization-to-c99-format.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Shubhrajyoti D <shubhrajyoti@xxxxxx> Subject: drivers/rtc/rtc-s35390a.c: convert struct i2c_msg initialization to C99 format Convert the struct i2c_msg initialization to C99 format. This makes maintaining and editing the code simpler. Also helps once other fields like transferred are added in future. Signed-off-by: Shubhrajyoti D <shubhrajyoti@xxxxxx> Reviewed-by: Felipe Balbi <balbi@xxxxxx> Cc: Alessandro Zummo <a.zummo@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/rtc/rtc-s35390a.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff -puN drivers/rtc/rtc-s35390a.c~drivers-rtc-rtc-s35390ac-convert-struct-i2c_msg-initialization-to-c99-format drivers/rtc/rtc-s35390a.c --- a/drivers/rtc/rtc-s35390a.c~drivers-rtc-rtc-s35390ac-convert-struct-i2c_msg-initialization-to-c99-format +++ a/drivers/rtc/rtc-s35390a.c @@ -50,7 +50,11 @@ static int s35390a_set_reg(struct s35390 { struct i2c_client *client = s35390a->client[reg]; struct i2c_msg msg[] = { - { client->addr, 0, len, buf }, + { + .addr = client->addr, + .len = len, + .buf = buf + }, }; if ((i2c_transfer(client->adapter, msg, 1)) != 1) @@ -63,7 +67,12 @@ static int s35390a_get_reg(struct s35390 { struct i2c_client *client = s35390a->client[reg]; struct i2c_msg msg[] = { - { client->addr, I2C_M_RD, len, buf }, + { + .addr = client->addr, + .flags = I2C_M_RD, + .len = len, + .buf = buf + }, }; if ((i2c_transfer(client->adapter, msg, 1)) != 1) _ Patches currently in -mm which might be from shubhrajyoti@xxxxxx are origin.patch linux-next.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html