From: Greg KH <gregkh@linuxfoundation.org>
To: Shubham Singh <dhoni.singh094@gmail.com>
Cc: forest@alittletooquite.net, devel@driver.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: vt6656: baseband.c: fixed unnecessary paranthesis
Date: Sat, 29 Sep 2018 02:34:39 -0700 [thread overview]
Message-ID: <20180929093439.GA30302@kroah.com> (raw)
In-Reply-To: <20180929085854.15880-1-dhoni.singh094@gmail.com>
On Sat, Sep 29, 2018 at 02:28:54PM +0530, Shubham Singh wrote:
> From: shubhsherl <dhoni.singh094@gmail.com>
>
> Fixed a coding line issue.
>
> Signed-off-by: shubhsherl <dhoni.singh094@gmail.com>
We need a real name please.
> ---
> drivers/staging/vt6656/baseband.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/vt6656/baseband.c b/drivers/staging/vt6656/baseband.c
> index b29ba237fa29..540cc9eafd07 100644
> --- a/drivers/staging/vt6656/baseband.c
> +++ b/drivers/staging/vt6656/baseband.c
> @@ -382,8 +382,8 @@ int vnt_vt3184_init(struct vnt_private *priv)
>
> dev_dbg(&priv->usb->dev, "RF Type %d\n", priv->rf_type);
>
> - if ((priv->rf_type == RF_AL2230) ||
> - (priv->rf_type == RF_AL2230S)) {
> + if (priv->rf_type == RF_AL2230 ||
> + priv->rf_type == RF_AL2230S) {
Huh? What coding style issue caused this? The original code is fine,
don't you agree? This type of change just makes it harder to work with
over time (hint, you have to go look up the order of operations all the
time...)
thanks
greg k-h
prev parent reply other threads:[~2018-09-29 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 8:58 [PATCH] Staging: vt6656: baseband.c: fixed unnecessary paranthesis Shubham Singh
2018-09-29 9:34 ` Greg KH [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=20180929093439.GA30302@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driver.osuosl.org \
--cc=dhoni.singh094@gmail.com \
--cc=forest@alittletooquite.net \
--cc=linux-kernel@vger.kernel.org \
/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.