From: Greg KH <gregkh@linuxfoundation.org>
To: Deepak R Varma <mh12gx2825@gmail.com>
Cc: outreachy-kernel@googlegroups.com, adham.abozaeid@microchip.com,
ajay.kathat@microchip.com, daniel.baluta@gmail.com
Subject: Re: [PATCH] wilc1000 : rearrange line exceeding 80 characters
Date: Tue, 10 Mar 2020 10:46:30 +0100 [thread overview]
Message-ID: <20200310094630.GA2514761@kroah.com> (raw)
In-Reply-To: <20200310092819.GA20959@deeUbuntu>
On Tue, Mar 10, 2020 at 02:58:24PM +0530, Deepak R Varma wrote:
> A long if condition exceeding 80 characters that makes evaluation
> appear confusing. Rearranging the condition makes it easier to understand.
>
> Signed-off-by: Deepak R Varma <mh12gx2825@gmail.com>
> ---
> drivers/staging/wilc1000/netdev.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
You forgot "staging:" in your subject line.
>
> diff --git a/drivers/staging/wilc1000/netdev.c b/drivers/staging/wilc1000/netdev.c
> index 045f5cdfdca0..d7a632c92a76 100644
> --- a/drivers/staging/wilc1000/netdev.c
> +++ b/drivers/staging/wilc1000/netdev.c
> @@ -802,8 +802,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)))
The original code is really easier to follow than your change, so I
would just leave it as-is please.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-10 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 9:28 [PATCH] wilc1000 : rearrange line exceeding 80 characters Deepak R Varma
2020-03-10 9:46 ` Greg KH [this message]
2020-03-10 11:04 ` Deepak Varma
2020-03-10 11:38 ` [Outreachy kernel] " Vaishali Thakkar
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=20200310094630.GA2514761@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adham.abozaeid@microchip.com \
--cc=ajay.kathat@microchip.com \
--cc=daniel.baluta@gmail.com \
--cc=mh12gx2825@gmail.com \
--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.