Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751080AbbF3Gnt (ORCPT ); Tue, 30 Jun 2015 02:43:49 -0400 Received: from mail-wg0-f48.google.com ([74.125.82.48]:34997 "EHLO mail-wg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750794AbbF3Gnl (ORCPT ); Tue, 30 Jun 2015 02:43:41 -0400 From: Fabio Falzoi To: thomas.petazzoni@free-electrons.com, noralf@tronnes.org Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, Fabio Falzoi Subject: [PATCH 00/10] Staging: fbtft: flexfb.c file clean up Date: Tue, 30 Jun 2015 08:43:07 +0200 Message-Id: <1435646597-7612-1-git-send-email-fabio.falzoi84@gmail.com> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1263 Lines: 30 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/