From: "Simon Sandström" <simon@nikanor.nu>
To: gregkh@linuxfoundation.org
Cc: forest@alittletooquiet.net, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org, "Simon Sandström" <simon@nikanor.nu>
Subject: [PATCH 0/4] staging: vt6656: Correct checkpatch.pl warnings
Date: Fri, 30 Jun 2017 23:38:50 +0200 [thread overview]
Message-ID: <20170630213854.4687-1-simon@nikanor.nu> (raw)
Here are some minor checkpatch.pl corrections to staging/vt6656.
I was about to ask before sending these in if you rather see commits
grouped on file or on type of warning, e.g. each commit fixes multiple
types of warnings in a single file versus each commit fixes one type
of warning in multiple files. It was easier to write commit messages
when grouped on type of warning, so that's what I did :-)
- Simon
---
Simon Sandström (4):
staging: vt6656: Add spaces between operators
staging: vt6656: Remove unnecessary blank lines
staging: vt6656: Align function parameters
staging: vt6656: Use variable instead of its type in sizeof(...)
drivers/staging/vt6656/device.h | 2 +-
drivers/staging/vt6656/firmware.c | 2 +-
drivers/staging/vt6656/key.h | 2 +-
drivers/staging/vt6656/main_usb.c | 5 ++---
drivers/staging/vt6656/power.c | 6 ++----
drivers/staging/vt6656/rf.c | 6 +++---
drivers/staging/vt6656/usbpipe.c | 4 ++--
7 files changed, 12 insertions(+), 15 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-30 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 21:38 Simon Sandström [this message]
2017-06-30 21:38 ` [PATCH 1/4] staging: vt6656: Add spaces between operators Simon Sandström
2017-06-30 21:38 ` [PATCH 2/4] staging: vt6656: Remove unnecessary blank lines Simon Sandström
2017-06-30 21:38 ` [PATCH 3/4] staging: vt6656: Align function parameters Simon Sandström
2017-06-30 21:38 ` [PATCH 4/4] staging: vt6656: Use variable instead of its type in sizeof(...) Simon Sandström
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=20170630213854.4687-1-simon@nikanor.nu \
--to=simon@nikanor.nu \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®