From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
liodot@gmail.com, charrer@alacritech.com
Subject: [PATCH 3/6] staging: slicoss: logical continuations should be on the previous line
Date: Fri, 18 Nov 2016 18:58:07 +0100 [thread overview]
Message-ID: <1479491890-10380-4-git-send-email-sergio.paracuellos@gmail.com> (raw)
In-Reply-To: <1479491890-10380-1-git-send-email-sergio.paracuellos@gmail.com>
Move logical or operator to previous line to comply with
the standard kernel coding style.
Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
drivers/staging/slicoss/slicoss.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c
index f8b956f..4ea5df6 100644
--- a/drivers/staging/slicoss/slicoss.c
+++ b/drivers/staging/slicoss/slicoss.c
@@ -614,8 +614,8 @@ static void slic_mac_config(struct adapter *adapter)
value |= GMCR_GBIT;
/* enable fullduplex */
- if ((adapter->linkduplex == LINK_FULLD)
- || (adapter->macopts & MAC_LOOPBACK)) {
+ if ((adapter->linkduplex == LINK_FULLD) ||
+ (adapter->macopts & MAC_LOOPBACK)) {
value |= GMCR_FULLD;
}
--
1.9.1
next prev parent reply other threads:[~2016-11-18 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 17:58 [PATCH 0/6] staging: slicoss: fix some style issues Sergio Paracuellos
2016-11-18 17:58 ` [PATCH 1/6] staging: slicoss: avoid CamelCases in slic.h Sergio Paracuellos
2016-11-18 17:58 ` [PATCH 2/6] staging: slicoss: fix parenthesis alignment in slicoss.c Sergio Paracuellos
2016-11-18 17:58 ` Sergio Paracuellos [this message]
2016-11-18 17:58 ` [PATCH 4/6] staging: slicoss: braces should be used on all arms of this statement Sergio Paracuellos
2016-11-18 17:58 ` [PATCH 5/6] staging: slicoss: avoid CamelCases in slichw.h Sergio Paracuellos
2016-11-18 17:58 ` [PATCH 6/6] staging: slicoss: avoid CamelCases slicoss.c Sergio Paracuellos
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=1479491890-10380-4-git-send-email-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=charrer@alacritech.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®