[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6df73f9b69434fc38411cd69172d7d57@HQMAIL111.nvidia.com>
Date: Mon, 21 Sep 2020 10:19:49 +0000
From: Thierry Reding <treding@...dia.com>
To: Dmitry Osipenko <digetx@...il.com>
CC: Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Wolfram Sang <wsa@...-dreams.de>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
Andy Shevchenko <andy.shevchenko@...il.com>,
<linux-i2c@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7 20/34] i2c: tegra: Remove "dma" variable from
tegra_i2c_xfer_msg()
On Wed, 09 Sep 2020 01:39:52 +0300, Dmitry Osipenko wrote:
> The "dma" variable of tegra_i2c_xfer_msg() function doesn't bring much in
> regards to readability and generation of the code.
>
> Besides readability, it's also not very nice that the is_curr_dma_xfer
> is initialized in tegra_i2c_xfer_msg() and then could be overridden by
> tegra_i2c_config_fifo_trig(). In a result, the "dma" variable creates
> slight confusion since it's not instantly obvious why it's set after
> tegra_i2c_config_fifo_trig().
>
> Hence should be better to have the variable removed. This makes code
> more consistent.
>
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
> Acked-by: Thierry Reding <treding@...dia.com>
> ---
> drivers/i2c/busses/i2c-tegra.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
Tested-by: Thierry Reding <treding@...dia.com>
Powered by blists - more mailing lists