public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jignesh R Patel <jigneshpatel0103@gmail.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Riley Andrews" <riandrews@android.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Jignesh R Patel <jigneshpatel0103@gmail.com>
Subject: [PATCH] Checkpatch: driver/staging in 4.2.0-rc4: Fix coding style problem
Date: Tue, 28 Jul 2015 15:28:33 +0530	[thread overview]
Message-ID: <1438077513-17898-1-git-send-email-jigneshpatel0103@gmail.com> (raw)

From: Jignesh R Patel <jigneshpatel0103@gmail.com>

This patch fix coding style problem of more then
80 character in one line. This patch does not change any
logic.

Signed-off-by: Jignesh R Patel <jigneshpatel0103@gmail.com>
---
 drivers/staging/android/ion/ion_cma_heap.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/android/ion/ion_cma_heap.c b/drivers/staging/android/ion/ion_cma_heap.c
index 86b91fd..4a9a7bd 100644
--- a/drivers/staging/android/ion/ion_cma_heap.c
+++ b/drivers/staging/android/ion/ion_cma_heap.c
@@ -73,7 +73,8 @@ static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer *buffer,
 	if (!info->table)
 		goto free_mem;
 
-	if (dma_get_sgtable(dev, info->table, info->cpu_addr, info->handle, len))
+	if (dma_get_sgtable(dev, info->table, info->cpu_addr,
+						info->handle, len))
 		goto free_table;
 	/* keep this for memory release */
 	buffer->priv_virt = info;
-- 
1.7.9.5


             reply	other threads:[~2015-07-28  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  9:58 Jignesh R Patel [this message]
2015-07-28 10:15 ` [PATCH] Checkpatch: driver/staging in 4.2.0-rc4: Fix coding style problem Dan Carpenter

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=1438077513-17898-1-git-send-email-jigneshpatel0103@gmail.com \
    --to=jigneshpatel0103@gmail.com \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riandrews@android.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