From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: w.d.hubbs@gmail.com
Cc: chris@the-brannons.com, outreachy-kernel@googlegroups.com,
kirk@reisers.ca, samuel.thibault@ens-lyon.org,
gregkh@linuxfoundation.org, speakup@linux-speakup.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Arushi Singhal <arushisinghal19971997@gmail.com>
Subject: [PATCH 0/6] multiple checkpatch issues
Date: Sat, 4 Mar 2017 01:47:03 +0530 [thread overview]
Message-ID: <20170303201709.19997-1-arushisinghal19971997@gmail.com> (raw)
Improve readability by fixing multiple checkpatch.pl
issues in speakup driver.
Arushi Singhal (6):
staging: speakup: Add blank line after function/struct/union/enum
declarations
staging: speakup: Logical continuations should be on the previous line
staging: speakup: Blank lines removed after an open brace '{'
staging: speakup: Avoid multiple assignments on same line
staging: speakup: fixes braces {} should be used on all arms of this
statement
staging: speakup: Comparison to NULL could be written
drivers/staging/speakup/kobjects.c | 1 -
drivers/staging/speakup/main.c | 85 ++++++++++++++++++++--------------
drivers/staging/speakup/selection.c | 2 +-
drivers/staging/speakup/serialio.c | 1 +
drivers/staging/speakup/speakup_dtlk.c | 1 +
drivers/staging/speakup/varhandlers.c | 6 +--
6 files changed, 55 insertions(+), 41 deletions(-)
--
2.11.0
next reply other threads:[~2017-03-03 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 20:17 Arushi Singhal [this message]
2017-03-03 20:17 ` [PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations Arushi Singhal
2017-03-09 13:25 ` Greg KH
[not found] ` <CA+XqjF_S9X5SmFo=AdSbPR8JnQvZzEye-xSnneF5eCm-6_G86Q@mail.gmail.com>
2017-03-09 16:24 ` Greg KH
2017-03-03 20:17 ` [PATCH 2/6] staging: speakup: Logical continuations should be on the previous line Arushi Singhal
2017-03-03 20:17 ` [PATCH 3/6] staging: speakup: Blank lines removed after an open brace '{' Arushi Singhal
2017-03-03 20:17 ` [PATCH 4/6] staging: speakup: Avoid multiple assignments on same line Arushi Singhal
2017-03-03 20:17 ` [PATCH 5/6] staging: speakup: fixes braces {} should be used on all arms of this statement Arushi Singhal
2017-03-03 20:17 ` [PATCH 6/6] staging: speakup: Comparison to NULL could be written Arushi Singhal
-- strict thread matches above, loose matches on Subject: below --
2017-03-04 15:57 [PATCH 0/6] multiple checkpatch issues Arushi Singhal
2017-03-03 18:37 Arushi Singhal
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=20170303201709.19997-1-arushisinghal19971997@gmail.com \
--to=arushisinghal19971997@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.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