From: Nadim almas <nadim.902@gmail.com>
To: sumit.semwal@linaro.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sarique <nadim.902@gmail.com>,
Nadim almas <nadim.902@gmail.com.com>
Subject: [PATCH 31/32] staging: android: ion: ion.c fixed a 80 character line limit coding style issue
Date: Sun, 24 Jul 2016 00:37:31 -0700 [thread overview]
Message-ID: <1469345851-3070-1-git-send-email-nadim.902@gmail.com> (raw)
From: sarique <nadim.902@gmail.com>
fixed a coding style issue.
Signed-off-by: Nadim almas <nadim.902@gmail.com.com>
---
drivers/staging/android/ion/ion.c | 3 ++-
drivers/staging/comedi/drivers/ssv_dnp.c | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c
index a2cf93b..52345df 100644
--- a/drivers/staging/android/ion/ion.c
+++ b/drivers/staging/android/ion/ion.c
@@ -1358,7 +1358,8 @@ static long ion_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
struct ion_handle *handle;
mutex_lock(&client->lock);
- handle = ion_handle_get_by_id_nolock(client, data.handle.handle);
+ handle = ion_handle_get_by_id_nolock(client,
+data.handle.handle);
if (IS_ERR(handle)) {
mutex_unlock(&client->lock);
return PTR_ERR(handle);
diff --git a/drivers/staging/comedi/drivers/ssv_dnp.c b/drivers/staging/comedi/drivers/ssv_dnp.c
index f9f634f..5674427 100644
--- a/drivers/staging/comedi/drivers/ssv_dnp.c
+++ b/drivers/staging/comedi/drivers/ssv_dnp.c
@@ -121,9 +121,9 @@ static int dnp_dio_insn_config(struct comedi_device *dev,
}
val = inb(CSCDR);
- if (data[0] == COMEDI_OUTPUT)
+ if (data[0] == COMEDI_OUTPUT)
val |= mask;
- else
+ else
val &= ~mask;
outb(val, CSCDR);
--
2.7.4
next reply other threads:[~2016-07-24 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 7:37 Nadim almas [this message]
2016-07-24 20:44 ` Greg KH
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=1469345851-3070-1-git-send-email-nadim.902@gmail.com \
--to=nadim.902@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nadim.902@gmail.com.com \
--cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome