From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: sudipm.mukherjee@gmail.com
Cc: teddy.wang@siliconmotion.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 v2 0/4] fix multiple checkpatch warnings
Date: Mon, 13 Mar 2017 21:47:56 +0530 [thread overview]
Message-ID: <20170313161800.17338-1-arushisinghal19971997@gmail.com> (raw)
Fix multiple code styling warnings issued by checkpatch on files
in sm750fb driver
Arushi Singhal (4):
staging: sm750fb: function prototype argument should have an
identifier name
staging: sm750fb: fixes add blank line after
function/struct/union/enum declarations
staging: sm750fb: Alignment should match open parenthesis
staging: sm750fb: Remove typedefs
drivers/staging/sm750fb/ddk750_display.h | 2 +-
drivers/staging/sm750fb/ddk750_mode.c | 83 ++++++++++++++++----------------
drivers/staging/sm750fb/ddk750_mode.h | 20 ++++----
drivers/staging/sm750fb/ddk750_power.h | 2 +-
drivers/staging/sm750fb/sm750.h | 4 +-
drivers/staging/sm750fb/sm750_cursor.c | 3 ++
drivers/staging/sm750fb/sm750_hw.c | 2 +-
7 files changed, 58 insertions(+), 58 deletions(-)
--
2.11.0
next reply other threads:[~2017-03-13 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 16:17 Arushi Singhal [this message]
2017-03-13 16:17 ` [PATCH v2 1/4] staging: sm750fb: function prototype argument should have an identifier name Arushi Singhal
2017-03-13 16:17 ` [PATCH v2 2/4] staging: sm750fb: fixes add blank line after function/struct/union/enum declarations Arushi Singhal
2017-03-13 16:17 ` [PATCH v2 3/4] staging: sm750fb: Alignment should match open parenthesis Arushi Singhal
2017-03-13 16:18 ` [PATCH v2 4/4] staging: sm750fb: Remove typedefs 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=20170313161800.17338-1-arushisinghal19971997@gmail.com \
--to=arushisinghal19971997@gmail.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=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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
all inboxes | Powered by JetHome®