mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Cláudio Maia" <crrm@isep.ipp.pt>
To: thomas.petazzoni@free-electrons.com, noralf@tronnes.org,
	gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] Staging: fbtft: fb_pcd8544: Fixed coding style errors and warnings
Date: Tue,  3 Mar 2015 23:47:18 +0000	[thread overview]
Message-ID: <1425426439-17358-1-git-send-email-crrm@isep.ipp.pt> (raw)

Fixed two warnings occurring in lines that are over 80 characters and which are not comments.

Signed-off-by: Cláudio Maia <crrm@isep.ipp.pt>
---
 drivers/staging/fbtft/fb_pcd8544.c |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/fbtft/fb_pcd8544.c b/drivers/staging/fbtft/fb_pcd8544.c
index 5e08a70..f25053c 100644
--- a/drivers/staging/fbtft/fb_pcd8544.c
+++ b/drivers/staging/fbtft/fb_pcd8544.c
@@ -94,7 +94,8 @@ static int init_display(struct fbtft_par *par)
 
 static void set_addr_win(struct fbtft_par *par, int xs, int ys, int xe, int ye)
 {
-	fbtft_par_dbg(DEBUG_SET_ADDR_WIN, par, "%s(xs=%d, ys=%d, xe=%d, ye=%d)\n", __func__, xs, ys, xe, ye);
+	fbtft_par_dbg(DEBUG_SET_ADDR_WIN, par, "%s(xs=%d, ys=%d, xe=%d, ye=%d)\n",
+			__func__, xs, ys, xe, ye);
 
 	/* H=0 Set X address of RAM */
 	write_reg(par, 0x80); /* 7:1  1
@@ -130,7 +131,8 @@ static int write_vmem(struct fbtft_par *par, size_t offset, size_t len)
 	gpio_set_value(par->gpio.dc, 1);
 	ret = par->fbtftops.write(par, par->txbuf.buf, 6*84);
 	if (ret < 0)
-		dev_err(par->info->device, "%s: write failed and returned: %d\n", __func__, ret);
+		dev_err(par->info->device, "%s: write failed and returned: %d\n",
+			__func__, ret);
 
 	return ret;
 }
-- 
1.7.9.5


             reply	other threads:[~2015-03-03 23:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 23:47 Cláudio Maia [this message]
2015-03-03 23:47 ` [PATCH 2/2] " Cláudio Maia
2015-03-04  5:22 ` [PATCH 1/2] " Sudip Mukherjee
  -- strict thread matches above, loose matches on Subject: below --
2015-03-04 11:11 Cláudio Maia
2015-03-07  0:45 ` Greg KH
2015-03-03 12:54 Cláudio Maia
2015-03-03 13:07 ` 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=1425426439-17358-1-git-send-email-crrm@isep.ipp.pt \
    --to=crrm@isep.ipp.pt \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --cc=thomas.petazzoni@free-electrons.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®