From: Stefano Brivio <sbrivio@redhat.com>
To: Gokce Kuler <gokcekuler@gmail.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [PATCH] staging: wilc1000: rearrange line exceeding 80 characters
Date: Tue, 17 Mar 2020 14:00:49 +0100 [thread overview]
Message-ID: <20200317140049.7c594147@elisabeth> (raw)
In-Reply-To: <20200316151009.GA7604@siyah2>
On Mon, 16 Mar 2020 18:10:09 +0300
Gokce Kuler <gokcekuler@gmail.com> wrote:
> Moved to the bottom line after && operator for it exceeds 80 character
>
> Signed-off-by: Gokce Kuler <gokcekuler@gmail.com>
> ---
> drivers/staging/wilc1000/netdev.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/wilc1000/netdev.c b/drivers/staging/wilc1000/netdev.c
> index a61c1a7..f94a17b 100644
> --- a/drivers/staging/wilc1000/netdev.c
> +++ b/drivers/staging/wilc1000/netdev.c
> @@ -794,8 +794,10 @@ void wilc_wfi_mgmt_rx(struct wilc *wilc, u8 *buff, u32 size)
> u16 type = le16_to_cpup((__le16 *)buff);
>
> if (vif->priv.p2p_listen_state &&
> - ((type == vif->frame_reg[0].type && vif->frame_reg[0].reg) ||
> - (type == vif->frame_reg[1].type && vif->frame_reg[1].reg)))
> + ((type == vif->frame_reg[0].type &&
> + vif->frame_reg[0].reg) ||
> + (type == vif->frame_reg[1].type &&
> + vif->frame_reg[1].reg)))
> wilc_wfi_p2p_rx(vif, buff, size);
Strictly speaking, your change is correct and this way the code
complies to the coding style.
Still, I tried to read the "fixed" version first, and it took me a
while to "vertically" track all those parentheses. Can you find a
better way to fix this?
--
Stefano
prev parent reply other threads:[~2020-03-17 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 15:10 [PATCH] staging: wilc1000: rearrange line exceeding 80 characters Gokce Kuler
2020-03-17 13:00 ` Stefano Brivio [this message]
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=20200317140049.7c594147@elisabeth \
--to=sbrivio@redhat.com \
--cc=gokcekuler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.