From: Dmitry Osipenko <digetx@gmail.com>
To: Jiada Wang <jiada_wang@mentor.com>,
nick@shmanahar.org, dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew_Gabbasov@mentor.com, erosca@de.adit-jv.com
Subject: Re: [PATCH v3 1/1] Input: atmel_mxt_ts - implement I2C retries
Date: Fri, 11 Sep 2020 18:10:37 +0300 [thread overview]
Message-ID: <0cd9055e-3ad5-f573-be39-3f999d9d461c@gmail.com> (raw)
In-Reply-To: <ec77e42c-ea72-bbae-e1b8-1e11cca17f87@gmail.com>
11.09.2020 18:05, Dmitry Osipenko пишет:
> 11.09.2020 17:50, Dmitry Osipenko пишет:
> ...
>>> @@ -626,6 +627,7 @@ static int __mxt_read_reg(struct i2c_client *client,
>>> struct i2c_msg xfer[2];
>>> u8 buf[2];
>>> int ret;
>>> + bool retry = false;
>
> Andy suggested to write this hunk like this:
>
> struct i2c_msg xfer[2];
> bool retry = false;
> u8 buf[2];
> int ret;
>
> This is not a mandatory request at all, but it will make this particular
> piece of code to look a bit nicer.
>
> There is also an opportunity to improve formatting of all variables by
> sorting them by-length across the whole driver, this will improve
> readability of the code. But of course it should be a separate patch.
> Please note that I'm *not* saying that you should create this separate
> patch!
>
I'd also recommend to rename the "retry" variable to "retried", which
will be a more logical name (more proper English).
next prev parent reply other threads:[~2020-09-11 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 15:16 [PATCH v3 1/1] Input: atmel_mxt_ts - implement I2C retries Jiada Wang
2020-09-11 14:50 ` Dmitry Osipenko
2020-09-11 15:05 ` Dmitry Osipenko
2020-09-11 15:10 ` Dmitry Osipenko [this message]
2020-09-14 13:49 ` Andy Shevchenko
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=0cd9055e-3ad5-f573-be39-3f999d9d461c@gmail.com \
--to=digetx@gmail.com \
--cc=Andrew_Gabbasov@mentor.com \
--cc=dmitry.torokhov@gmail.com \
--cc=erosca@de.adit-jv.com \
--cc=jiada_wang@mentor.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.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).