[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f439c33c8f09da9f0fe44e8eebd98286c3e1e3e.camel@perches.com>
Date: Mon, 31 May 2021 08:49:22 -0700
From: Joe Perches <joe@...ches.com>
To: Raviteja Narayanam <raviteja.narayanam@...inx.com>,
linux-i2c@...r.kernel.org, michal.simek@...inx.com
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
git@...inx.com, marex@...x.de
Subject: Re: [PATCH 03/10] i2c: xiic: Fix coding style issues
On Mon, 2021-05-31 at 07:19 -0600, Raviteja Narayanam wrote:
> From: Michal Simek <michal.simek@...inx.com>
>
> Most of these stuff are reported by checkpatch.
trivia:
> diff --git a/drivers/i2c/busses/i2c-xiic.c b/drivers/i2c/busses/i2c-xiic.c
[]
> @@ -519,8 +522,8 @@ static irqreturn_t xiic_process(int irq, void *dev_id)
>
>
> /* Service requesting interrupt */
> if ((pend & XIIC_INTR_ARB_LOST_MASK) ||
> - ((pend & XIIC_INTR_TX_ERROR_MASK) &&
> - !(pend & XIIC_INTR_RX_FULL_MASK))) {
> + ((pend & XIIC_INTR_TX_ERROR_MASK) &&
> + !(pend & XIIC_INTR_RX_FULL_MASK))) {
This last line would more commonly be indented one more space to
align to the appropriate open parenthesis depth.
tab then 4 spaces for
((pend & XIIC_INTR_TX_ERROR_MASK) &&
tab then 5 spaces for
!(pend & XIIC_INTR_RX_FULL_MASK))) {
Powered by blists - more mailing lists