mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabio Falzoi <fabio.falzoi84@gmail.com>
To: thomas.petazzoni@free-electrons.com, noralf@tronnes.org
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Fabio Falzoi <fabio.falzoi84@gmail.com>
Subject: [PATCH 00/10] Staging: fbtft: flexfb.c file clean up
Date: Tue, 30 Jun 2015 08:43:07 +0200	[thread overview]
Message-ID: <1435646597-7612-1-git-send-email-fabio.falzoi84@gmail.com> (raw)

This patchset aims to refactor the code in flexfb.c, making it more
readable and maintanable.
Various checkpatch.pl issues are fixed.
These patches are created on top of greg-kh's linux-staging tree,
staging-testing branch.

Fabio Falzoi (10):
  Staging: fbtft: Remove paragraph about writing to FSF
  Staging: fbtft: Remove unnecessary multiple blank lines
  Staging: fbtft: Use a struct to describe each LCD controller
  Staging: fbtft: Use a helper function to set write_register op
  Staging: fbtft: Set bus specific ops using separate functions
  Staging: fbtft: Use a helper function to set set_addr_win op
  Staging: fbtft: Remove useless newline
  Staging: fbtft: Avoid duplicating code to check gpio.dc value
  Staging: fbtft: Fix parenthesis alignment coding style issue
  Staging: fbtft: Fix spacing coding style issue

 drivers/staging/fbtft/fbtft.h  |  20 ++
 drivers/staging/fbtft/flexfb.c | 485 +++++++++++++++++++++++------------------
 2 files changed, 289 insertions(+), 216 deletions(-)

-- 
2.1.4


             reply	other threads:[~2015-06-30  6:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  6:43 Fabio Falzoi [this message]
2015-06-30  6:43 ` [PATCH 01/10] Staging: fbtft: Remove paragraph about writing to FSF Fabio Falzoi
2015-06-30  6:43 ` [PATCH 02/10] Staging: fbtft: Remove unnecessary multiple blank lines Fabio Falzoi
2015-06-30  6:43 ` [PATCH 03/10] Staging: fbtft: Use a struct to describe each LCD controller Fabio Falzoi
2015-07-15  2:12   ` Greg KH
2015-07-23 11:09   ` Noralf Trønnes
2015-08-02 14:57     ` [PATCH v2] " Fabio Falzoi
2015-08-02 17:54       ` Noralf Trønnes
2015-08-02 20:17         ` Fabio Falzoi
2015-08-02 20:30         ` [PATCH v3] " Fabio Falzoi
2015-06-30  6:43 ` [PATCH 04/10] Staging: fbtft: Use a helper function to set write_register op Fabio Falzoi
2015-07-15  2:13   ` Greg KH
2015-06-30  6:43 ` [PATCH 05/10] Staging: fbtft: Set bus specific ops using separate functions Fabio Falzoi
2015-07-15  2:13   ` Greg KH
2015-06-30  6:43 ` [PATCH 06/10] Staging: fbtft: Use a helper function to set set_addr_win op Fabio Falzoi
2015-07-15  2:14   ` Greg KH
2015-07-23 11:19     ` Noralf Trønnes
2015-06-30  6:43 ` [PATCH 07/10] Staging: fbtft: Remove useless newline Fabio Falzoi
2015-06-30  7:42   ` Dan Carpenter
2015-06-30 14:55     ` Joe Perches
2015-06-30 17:45       ` Dan Carpenter
2015-06-30 19:03         ` Joe Perches
2015-06-30  6:43 ` [PATCH 08/10] Staging: fbtft: Avoid duplicating code to check gpio.dc value Fabio Falzoi
2015-06-30  6:43 ` [PATCH 09/10] Staging: fbtft: Fix parenthesis alignment coding style issue Fabio Falzoi
2015-06-30  6:43 ` [PATCH 10/10] Staging: fbtft: Fix spacing " Fabio Falzoi

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=1435646597-7612-1-git-send-email-fabio.falzoi84@gmail.com \
    --to=fabio.falzoi84@gmail.com \
    --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®