From: Bogdan Purcareata <bogdan.purcareata@gmail.com>
To: labbott@redhat.com, sumit.semwal@linaro.org,
gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: Bogdan Purcareata <bogdan.purcareata@gmail.com>
Subject: [PATCH 1/4] staging: android/ion: Fix line over 80 characters
Date: Thu, 12 Jan 2017 09:54:16 +0200 [thread overview]
Message-ID: <1484207659-22702-1-git-send-email-bogdan.purcareata@gmail.com> (raw)
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@gmail.com>
---
drivers/staging/android/ion/ion-ioctl.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/android/ion/ion-ioctl.c b/drivers/staging/android/ion/ion-ioctl.c
index 7e7431d..e28fffb 100644
--- a/drivers/staging/android/ion/ion-ioctl.c
+++ b/drivers/staging/android/ion/ion-ioctl.c
@@ -111,7 +111,8 @@ 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);
--
2.7.4
next reply other threads:[~2017-01-12 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 7:54 Bogdan Purcareata [this message]
2017-01-12 7:54 ` [PATCH 2/4] staging: android/ion: Don't use return in void function Bogdan Purcareata
2017-01-12 7:54 ` [PATCH 3/4] staging: android/ion: Align comment mark Bogdan Purcareata
2017-01-12 7:54 ` [PATCH 4/4] staging: android/ion: Use variable names in header Bogdan Purcareata
2017-01-12 9:32 ` [PATCH 1/4] staging: android/ion: Fix line over 80 characters Dan Carpenter
2017-01-12 9:56 ` Greg KH
2017-01-12 21:45 ` Bogdan Purcareata
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=1484207659-22702-1-git-send-email-bogdan.purcareata@gmail.com \
--to=bogdan.purcareata@gmail.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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
all inboxes | Powered by JetHome®