From: Gargi Sharma <gs051095@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: arnaud.patard@rtp-net.org, gregkh@linuxfoundation.org,
Gargi Sharma <gs051095@gmail.com>
Subject: [PATCH 0/6] Cleaning xgifb/vb_setmode.c
Date: Wed, 14 Sep 2016 05:20:59 +0530 [thread overview]
Message-ID: <cover.1473809550.git.gs051095@gmail.com> (raw)
This patchset fixes various issues that come up in the checkpatch in patch 1, 3, 4 and 5. Patches 2 and 6 are based on Julia's suggestion when a one patch was sent fixing the checkpatch issue of moving && operator to previous line.
Gargi Sharma (6):
staging: xgifb: move AND operator for logical continuation
staging: xgifb: remove unnecessary parentheses
staging: xgifb: remove blank line after open brace
staging: xgifb: add spaces around |
staging: xgifb: remove blank line before closing brace
staging: xgifb: fix alignment for if arguments
drivers/staging/xgifb/vb_setmode.c | 48 ++++++++++++++------------------------
1 file changed, 17 insertions(+), 31 deletions(-)
--
2.9.2
next reply other threads:[~2016-09-13 23:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 23:50 Gargi Sharma [this message]
2016-09-13 23:51 ` [PATCH 1/6] staging: xgifb: move AND operator for logical continuation Gargi Sharma
2016-09-14 5:43 ` [Outreachy kernel] " Julia Lawall
2016-09-13 23:51 ` [PATCH 2/6] staging: xgifb: remove unnecessary parentheses Gargi Sharma
2016-09-14 5:46 ` [Outreachy kernel] " Julia Lawall
2016-09-13 23:51 ` [PATCH 3/6] staging: xgifb: remove blank line after open brace Gargi Sharma
2016-09-13 23:51 ` [PATCH 4/6] staging: xgifb: add spaces around | Gargi Sharma
2016-09-13 23:51 ` [PATCH 5/6] staging: xgifb: remove blank line before closing brace Gargi Sharma
2016-09-13 23:51 ` [PATCH 6/6] staging: xgifb: fix alignment for if arguments Gargi Sharma
2016-09-14 5:48 ` [Outreachy kernel] " Julia Lawall
2016-09-14 5:41 ` [Outreachy kernel] [PATCH 0/6] Cleaning xgifb/vb_setmode.c Julia Lawall
2016-09-14 9:16 ` Gargi Sharma
2016-09-14 9:21 ` Vaishali Thakkar
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.1473809550.git.gs051095@gmail.com \
--to=gs051095@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=gregkh@linuxfoundation.org \
--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 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.