From: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>
To: gregkh@linuxfoundation.org
Cc: outreachy-kernel@googlegroups.com,
saiprakash.ranjan@codeaurora.org, joel@joelfernandes.org,
Forest Bond <forest@alittletooquiet.net>
Subject: [PATCH 0/3] staging: vt6655: Fix alignment, spacing and open-ended lines
Date: Fri, 1 Nov 2019 04:20:14 +0000 [thread overview]
Message-ID: <cover.1572581578.git.frank@generalsoftwareinc.com> (raw)
This patchset fixes minor spacing, alignment, and open-ended lines.
Three types of checkpatch.pl messages are addressed:
- CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
- CHECK:SPACING: spaces preferred around that
- CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
Frank A. Cancio Bello (3):
staging: vt6655: Fix parameters alignment issues
staging: vt6655: Fix the spacing around operators
staging: vt6655: Fix open ended lines
drivers/staging/vt6655/card.h | 2 +-
drivers/staging/vt6655/device_main.c | 14 ++++++++------
drivers/staging/vt6655/power.c | 10 ++--------
drivers/staging/vt6655/rf.c | 4 ++--
drivers/staging/vt6655/rf.h | 19 +++++--------------
drivers/staging/vt6655/rxtx.c | 5 +++--
6 files changed, 21 insertions(+), 33 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-01 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 4:20 Frank A. Cancio Bello [this message]
2019-11-01 4:20 ` [PATCH 1/3] staging: vt6655: Fix parameters alignment issues Frank A. Cancio Bello
2019-11-01 7:32 ` [Outreachy kernel] " Julia Lawall
2019-11-01 4:21 ` [PATCH 2/3] staging: vt6655: Fix the spacing around operators Frank A. Cancio Bello
2019-11-01 4:22 ` [PATCH 3/3] staging: vt6655: Fix open ended lines Frank A. Cancio Bello
2019-11-01 7:34 ` [Outreachy kernel] [PATCH 0/3] staging: vt6655: Fix alignment, spacing and open-ended lines Julia Lawall
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=cover.1572581578.git.frank@generalsoftwareinc.com \
--to=frank@generalsoftwareinc.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=saiprakash.ranjan@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.