From: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
To: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
nishkadg.linux@gmail.com, kim.jamie.bradley@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org
Cc: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
Subject: [PATCH v3 0/3] staging: rts5208: Eliminate the use of Camel Case
Date: Wed, 30 Oct 2019 16:05:11 -0300 [thread overview]
Message-ID: <20191030190514.10011-1-gabrielabittencourt00@gmail.com> (raw)
Cleans up checks of "Avoid CamelCase" in tree rts5208
Changes in v3:
- Change the subject line of commits to make it more clear and informative
Changes in v2:
- Place the changes on variable's names in the use and definition in the
same commit
I compile the kernel after each commit of the series to make sure it
doesn't break the compilation.
Gabriela Bittencourt (3):
staging: rts5208: Eliminate the use of Camel Case in files ms.{h,c}
staging: rts5208: Eliminate the use of Camel Case in files xd.{h,c}
staging: rts5208: Eliminate the use of Camel Case in file sd.h
drivers/staging/rts5208/ms.c | 86 ++++++++++++++++++------------------
drivers/staging/rts5208/ms.h | 70 ++++++++++++++---------------
drivers/staging/rts5208/sd.h | 2 +-
drivers/staging/rts5208/xd.c | 8 ++--
drivers/staging/rts5208/xd.h | 6 +--
5 files changed, 86 insertions(+), 86 deletions(-)
--
2.20.1
next reply other threads:[~2019-10-30 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 19:05 Gabriela Bittencourt [this message]
2019-10-30 19:05 ` [PATCH v3 1/3] staging: rts5208: Eliminate the use of Camel Case in files ms.{h,c} Gabriela Bittencourt
2019-10-31 6:40 ` [Outreachy kernel] " Julia Lawall
2019-10-30 19:05 ` [PATCH v3 2/3] staging: rts5208: Eliminate the use of Camel Case in files xd.{h,c} Gabriela Bittencourt
2019-10-31 6:39 ` [Outreachy kernel] " Julia Lawall
2019-10-30 19:05 ` [PATCH v3 3/3] staging: rts5208: Eliminate the use of Camel Case in file sd.h Gabriela Bittencourt
2019-10-31 6:35 ` [Outreachy kernel] " 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=20191030190514.10011-1-gabrielabittencourt00@gmail.com \
--to=gabrielabittencourt00@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kim.jamie.bradley@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=nishkadg.linux@gmail.com \
--cc=outreachy-kernel@googlegroups.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).