From: Mike Rapoport <mike.rapoport@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Mike Rapoport" <mike.rapoport@gmail.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/5] staging: fbtft: some checpatch.pl cleanups
Date: Thu, 3 Sep 2015 08:13:09 +0300 [thread overview]
Message-ID: <1441257194-19493-1-git-send-email-mike.rapoport@gmail.com> (raw)
Hi,
These patches slightly refactor the code to reduce amount of checkpath.pl
warnings
v2 changes:
* add elaborate changelog to the first pacth in the series (staging: fbtft:
remove unused bl_ops from fbtft_unregister_backlight)
Mike Rapoport (5):
staging: fbtft: remove unused bl_ops from fbtft_unregister_backlight
staging: fbtft: fbtft-core: define backlight_ops statically
staging: fbtft: fbtft_request_gpios: reduce nesting
staging: fbtft: fb_ssd1351: define backlight_ops statically
staging: fbtft: fb_watterott: define backlight_ops statically
drivers/staging/fbtft/fb_ssd1351.c | 13 +++----
drivers/staging/fbtft/fb_watterott.c | 17 +++------
drivers/staging/fbtft/fbtft-core.c | 69 +++++++++++++++++-------------------
3 files changed, 42 insertions(+), 57 deletions(-)
--
2.1.0
next reply other threads:[~2015-09-03 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 5:13 Mike Rapoport [this message]
2015-09-03 5:13 ` [PATCH v2 1/5] staging: fbtft: remove unused bl_ops from fbtft_unregister_backlight Mike Rapoport
2015-09-03 5:13 ` [PATCH v2 2/5] staging: fbtft: fbtft-core: define backlight_ops statically Mike Rapoport
2015-09-03 5:13 ` [PATCH v2 3/5] staging: fbtft: fbtft_request_gpios: reduce nesting Mike Rapoport
2015-09-03 5:13 ` [PATCH v2 4/5] staging: fbtft: fb_ssd1351: define backlight_ops statically Mike Rapoport
2015-09-03 5:13 ` [PATCH v2 5/5] staging: fbtft: fb_watterott: " Mike Rapoport
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=1441257194-19493-1-git-send-email-mike.rapoport@gmail.com \
--to=mike.rapoport@gmail.com \
--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®