From: Rehas Sachdeva <aquannie@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/5] staging: sm750fb: Fix multiple checkpatch warnings
Date: Fri, 16 Sep 2016 03:01:50 +0530 [thread overview]
Message-ID: <cover.1473975000.git.aquannie@gmail.com> (raw)
Fixes multiple checkpatch warnings in sm750fb driver.
Rehas Sachdeva (5):
staging: sm750fb: Add blank line after declarations
staging: sm750fb: Change 'x != NULL' to 'x'
staging: sm750fb: Remove multiple assignments
staging: sm750fb: Change 'uint32_t' to 'u32'
staging: sm750fb: Add spaces around '|'
drivers/staging/sm750fb/ddk750_chip.h | 3 +++
drivers/staging/sm750fb/ddk750_display.h | 45 ++++++++++++++++----------------
drivers/staging/sm750fb/ddk750_mode.h | 2 ++
drivers/staging/sm750fb/ddk750_power.h | 1 +
drivers/staging/sm750fb/sm750.c | 14 ++++++----
drivers/staging/sm750fb/sm750_cursor.c | 3 +++
drivers/staging/sm750fb/sm750_hw.c | 2 +-
7 files changed, 42 insertions(+), 28 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-15 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 21:31 Rehas Sachdeva [this message]
2016-09-15 21:32 ` [PATCH 1/5] staging: sm750fb: Add blank line after declarations Rehas Sachdeva
2016-09-16 7:48 ` Greg Kroah-Hartman
2016-09-16 7:53 ` [Outreachy kernel] " Julia Lawall
2016-09-15 21:32 ` [PATCH 2/5] staging: sm750fb: Change 'x != NULL' to 'x' Rehas Sachdeva
2016-09-15 21:33 ` [PATCH 3/5] staging: sm750fb: Remove multiple assignments Rehas Sachdeva
2016-09-16 7:48 ` Greg Kroah-Hartman
2016-09-16 12:34 ` Rehas Sachdeva
2016-09-16 12:55 ` Greg Kroah-Hartman
2016-09-15 21:33 ` [PATCH 4/5] staging: sm750fb: Change 'uint32_t' to 'u32' Rehas Sachdeva
2016-09-15 21:33 ` [PATCH 5/5] staging: sm750fb: Add spaces around '|' Rehas Sachdeva
2016-09-16 7:50 ` Greg Kroah-Hartman
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.1473975000.git.aquannie@gmail.com \
--to=aquannie@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.