From: Aymen Qader <qader.aymen@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Aymen Qader <qader.aymen@gmail.com>,
Eric Anholt <eric@anholt.net>,
Stefan Wahren <stefan.wahren@i2se.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/4] staging: vc04_services: Fix checkpatch.pl errors
Date: Mon, 24 Sep 2018 18:35:43 +0100 [thread overview]
Message-ID: <20180924173547.23393-1-qader.aymen@gmail.com> (raw)
This patchset fixes the following checkpatch.pl errors in the
interface/vchi directory:
ERROR: space prohibited after/before that open/closed parenthesis
ERROR: code indent should use tabs where possible
ERROR: space required after that ','
ERROR: Macros with complex values should be enclosed in parentheses
ERROR: "foo * bar" should be "foo* bar"
Aymen Qader (4):
staging: vc04_services: Fix "space prohibited"
staging: vc04_services: Use tabs instead of spaces
staging: vc04_services: Remove unused macros
staging: vc04_services: Remove spaces after '*'
v2: Added cover letter correctly
v3: Remove unused macros
v4: Added patch changelog to cover letter
.../vc04_services/interface/vchi/vchi.h | 208 +++++++-----------
.../vc04_services/interface/vchi/vchi_cfg.h | 2 +-
2 files changed, 86 insertions(+), 124 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-24 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 17:35 Aymen Qader [this message]
2018-09-24 17:35 ` [PATCH v4 1/4] staging: vc04_services: Fix "space prohibited" Aymen Qader
2018-09-24 17:35 ` [PATCH v4 2/4] staging: vc04_services: Use tabs instead of spaces Aymen Qader
2018-09-24 17:35 ` [PATCH v4 3/4] staging: vc04_services: Remove unused macros Aymen Qader
2018-09-24 17:35 ` [PATCH v4 4/4] staging: vc04_services: Remove spaces after '*' Aymen Qader
2018-09-25 7:15 ` [PATCH v4 0/4] staging: vc04_services: Fix checkpatch.pl errors Dan Carpenter
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=20180924173547.23393-1-qader.aymen@gmail.com \
--to=qader.aymen@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).