linux-kernel - [PATCH 00/10] Staging: fbtft: flexfb.c file clean up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1435646597-7612-1-git-send-email-fabio.falzoi84@gmail.com>
Date:	Tue, 30 Jun 2015 08:43:07 +0200
From:	Fabio Falzoi <fabio.falzoi84@...il.com>
To:	thomas.petazzoni@...e-electrons.com, noralf@...nnes.org
Cc:	gregkh@...uxfoundation.org, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org,
	Fabio Falzoi <fabio.falzoi84@...il.com>
Subject: [PATCH 00/10] Staging: fbtft: flexfb.c file clean up

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/