All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heba Aamer <heba93aamer@gmail.com>
To: devel@driverdev.osuosl.org
Cc: gregkh@linuxfoundation.org, notro@tronnes.org,
	thomas.petazzoni@free-electrons.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] Fix fbtft/fb_pcd8544.c coding style errors
Date: Tue, 27 Jan 2015 22:30:15 +0200	[thread overview]
Message-ID: <cover.1422296762.git.heba93aamer@gmail.com> (raw)

This patch set fixes most of the checkpatch.pl coding
style errors found in drivers/staging/fbtft/fb_pcd8544.c

Heba Aamer (6):
  staging: fbtft: fix space required after that ';'
  staging: fbtft: fix spaces required around that '='
  staging: fbtft: fix spaces required around that '<'
  staging: fbtft: fix Macros with complex values should be enclosed in
    parentheses
  staging: fbtft: fix do not initialise statics to 0 or NULL
  staging: fbtft: fix trailing whitespace

 drivers/staging/fbtft/fb_pcd8544.c |   16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2015-01-27 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 20:30 Heba Aamer [this message]
2015-01-27 20:33 ` [PATCH 1/6] staging: fbtft: fix space required after that ';' Heba Aamer
2015-01-27 20:35 ` [PATCH 2/6] staging: fbtft: fix spaces required around that '=' Heba Aamer
2015-01-27 20:37 ` [PATCH 3/6] staging: fbtft: fix spaces required around that '<' Heba Aamer
2015-01-27 20:39 ` [PATCH 4/6] staging: fbtft: fix Macros with complex values should be enclosed in parentheses Heba Aamer
2015-01-27 20:42 ` [PATCH 5/6] staging: fbtft: fix do not initialise statics to 0 or NULL Heba Aamer
2015-01-27 20:46 ` [PATCH 6/6] staging: fbtft: fix trailing whitespace Heba Aamer
2015-01-27 20:47 ` [PATCH 0/6] Fix fbtft/fb_pcd8544.c coding style errors Joe Perches

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=cover.1422296762.git.heba93aamer@gmail.com \
    --to=heba93aamer@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notro@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.