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 v2 0/4] staging: vt6655: Code style cleanup
Date: Fri, 1 Nov 2019 23:20:59 +0000 [thread overview]
Message-ID: <cover.1572649242.git.frank@generalsoftwareinc.com> (raw)
Code style issues like wrong spacing, long lines, open ended parameter
and alignment make the code harder to read. This patchset improves the
code to comply with the preferred coding style for the linux kernel.
Issues found by checkpatch.
Changes in v2 by Julia Lawall suggestion:
- Improves log messages on all of the patches.
- Remove the checkpatch messages.
- Long line issues are in its own patch.
Frank A. Cancio Bello (4):
staging: vt6655: Fix parameter alignment issues
staging: vt6655: Fix the spacing around operators
staging: vt6655: Fix open ended lines
staging: vt6655: Fix long 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 | 5 +++--
drivers/staging/vt6655/rf.h | 19 +++++--------------
drivers/staging/vt6655/rxtx.c | 5 +++--
6 files changed, 22 insertions(+), 33 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-01 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 23:20 Frank A. Cancio Bello [this message]
2019-11-01 23:21 ` [PATCH v2 1/4] staging: vt6655: Fix parameter alignment issues Frank A. Cancio Bello
2019-11-01 23:22 ` [PATCH v2 2/4] staging: vt6655: Fix the spacing around operators Frank A. Cancio Bello
2019-11-01 23:23 ` [PATCH v2 3/4] staging: vt6655: Fix open ended lines Frank A. Cancio Bello
2019-11-01 23:25 ` [PATCH v2 4/4] staging: vt6655: Fix long lines Frank A. Cancio Bello
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.1572649242.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.