From: Ira Weiny <ira.weiny@intel.com>
To: Khadija Kamran <kamrankhadijadj@gmail.com>, <outreachy@lists.linux.dev>
Cc: Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<greybus-dev@lists.linaro.org>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] staging: greybus: remove tabs to fix line length and merge lines
Date: Sun, 12 Mar 2023 18:01:03 -0700 [thread overview]
Message-ID: <640e75cfd8fc_229a89294a3@iweiny-mobl.notmuch> (raw)
In-Reply-To: <ZAusnKYVTGvO5zoi@khadija-virtual-machine>
Khadija Kamran wrote:
> In file drivers/staging/greybus/arche-platform.c,
> - Length of line 181 exceeds 100 columns, fix by removing tabs from the
> line.
> - If condition and spin_unlock_...() call is split into two lines, join
> them to form a single line.
>
> Signed-off-by: Khadija Kamran <kamrankhadijadj@gmail.com>
Fundamentally the problem with arche_platform_wd_irq() is that the
indentation is too great.
"... if you need more than 3 levels of indentation, you’re screwed anyway,
and should fix your program."
-- https://www.kernel.org/doc/html/v4.10/process/coding-style.html#indentation
I think a better solution would be to refactor the entire function. This
would make the logic of the function more clear as well IMHO.
Here is another tip to help:
https://www.kernel.org/doc/html/v4.10/process/coding-style.html#centralized-exiting-of-functions
Do you think you could try that?
Ira
> ---
> Changes in v2:
> - Change the subject and log message
> - Merge if condition and spin_unlock...() from two lines to one
> drivers/staging/greybus/arche-platform.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/greybus/arche-platform.c b/drivers/staging/greybus/arche-platform.c
> index fcbd5f71eff2..00ed5dfd7915 100644
> --- a/drivers/staging/greybus/arche-platform.c
> +++ b/drivers/staging/greybus/arche-platform.c
> @@ -176,12 +176,10 @@ static irqreturn_t arche_platform_wd_irq(int irq, void *devid)
> * Check we are not in middle of irq thread
> * already
> */
> - if (arche_pdata->wake_detect_state !=
> - WD_STATE_COLDBOOT_START) {
> + if (arche_pdata->wake_detect_state != WD_STATE_COLDBOOT_START) {
> arche_platform_set_wake_detect_state(arche_pdata,
> - WD_STATE_COLDBOOT_TRIG);
> - spin_unlock_irqrestore(&arche_pdata->wake_lock,
> - flags);
> + WD_STATE_COLDBOOT_TRIG);
> + spin_unlock_irqrestore(&arche_pdata->wake_lock, flags);
> return IRQ_WAKE_THREAD;
> }
> }
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-03-13 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 22:18 [PATCH v2] staging: greybus: remove tabs to fix line length and merge lines Khadija Kamran
2023-03-11 4:16 ` Dan Carpenter
2023-03-11 6:24 ` Khadija Kamran
2023-03-11 7:05 ` Deepak R Varma
2023-03-11 7:16 ` Khadija Kamran
2023-03-11 8:48 ` Julia Lawall
2023-03-13 1:01 ` Ira Weiny [this message]
2023-03-20 8:53 ` Khadija Kamran
2023-03-21 0:33 ` Ira Weiny
2023-03-21 17:00 ` Khadija Kamran
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=640e75cfd8fc_229a89294a3@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=hvaibhav.linux@gmail.com \
--cc=johan@kernel.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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