From: Rishabh Hardas <rishabhhardas@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux@Wolf-Entwicklungen.de, rjosephwright@gmail.com,
colin.king@canonical.com, robsonde@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Rishabh Hardas <rishabhhardas@gmail.com>
Subject: [PATCH v2 0/4] staging: pi433: Rename camel case and other style issues
Date: Thu, 3 Aug 2017 17:20:42 +0530 [thread overview]
Message-ID: <cover.1501759442.git.rishabhhardas@gmail.com> (raw)
Hi,
This series pf patches solves some of the coding style
issues. I have corrected long lines, changed comment style,
renamed enums and variables that were in camel case.
Tried to get zero erros and warnings on the pi433_if.h file.
Regards,
Rishabh Hardas
Rishabh Hardas (4):
staging: pi433: Style fix - Correct long lines
staging: pi433: Change Comments
staging: pi433: Renaming Enums
staging: pi433: Remove camel case variable names
drivers/staging/pi433/pi433_if.c | 4 +--
drivers/staging/pi433/pi433_if.h | 73 +++++++++++++++++++++------------------
drivers/staging/pi433/rf69.c | 26 +++++++-------
drivers/staging/pi433/rf69.h | 26 +++++++-------
drivers/staging/pi433/rf69_enum.h | 16 ++++-----
5 files changed, 76 insertions(+), 69 deletions(-)
--
1.9.1
next reply other threads:[~2017-08-03 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 11:50 Rishabh Hardas [this message]
2017-08-03 11:50 ` [PATCH v2 1/4] staging: pi433: Style fix - Correct long lines Rishabh Hardas
2017-08-15 0:42 ` Greg KH
2017-08-16 7:31 ` Dan Carpenter
2017-08-20 4:47 ` Joe Perches
2017-08-22 9:27 ` Rishabh Hardas
2017-08-22 10:03 ` Dan Carpenter
2017-08-22 10:29 ` Marcus Wolf
2017-08-22 10:43 ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 2/4] staging: pi433: Change Comments Rishabh Hardas
2017-08-16 7:35 ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 3/4] staging: pi433: Renaming Enums Rishabh Hardas
2017-08-16 7:34 ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 4/4] staging: pi433: Remove camel case variable names Rishabh Hardas
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.1501759442.git.rishabhhardas@gmail.com \
--to=rishabhhardas@gmail.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@Wolf-Entwicklungen.de \
--cc=rjosephwright@gmail.com \
--cc=robsonde@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
Powered by JetHome