From: Gargi Sharma <gs051095@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org, Gargi Sharma <gs051095@gmail.com>
Subject: [PATCH 0/8] fix multiple checkpatch issues
Date: Fri, 16 Sep 2016 08:16:02 +0530 [thread overview]
Message-ID: <cover.1473993585.git.gs051095@gmail.com> (raw)
Fix issues detected using checkpatch.pl
Gargi Sharma (8):
staging: wlan-ng: add spaces around +
staging: wlan-ng: add spaces around &
staging: wlan-ng: add spaces around >>
staging: wlan-ng: add spaces around |
staging: wlan-ng: add spaces around <<
staging: wlan-ng: delete space after a cast
staging: wlan-ng: add blank line after declaration
staging: wlan-ng: fix block comment style
drivers/staging/wlan-ng/hfa384x.h | 251 +++++++++--------
pace | 567 ++++++++++++++++++++++++++++++++++++++
2 files changed, 707 insertions(+), 111 deletions(-)
create mode 100644 pace
--
2.9.2
next reply other threads:[~2016-09-16 2:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 2:46 Gargi Sharma [this message]
2016-09-16 2:46 ` [PATCH 1/8] staging: wlan-ng: add spaces around + Gargi Sharma
2016-09-16 2:46 ` [PATCH 2/8] staging: wlan-ng: add spaces around & Gargi Sharma
2016-09-16 2:46 ` [PATCH 3/8] staging: wlan-ng: add spaces around >> Gargi Sharma
2016-09-16 5:41 ` [Outreachy kernel] " Julia Lawall
2016-09-16 2:46 ` [PATCH 4/8] staging: wlan-ng: add spaces around | Gargi Sharma
2016-09-16 2:46 ` [PATCH 5/8] staging: wlan-ng: add spaces around << Gargi Sharma
2016-09-16 5:39 ` [Outreachy kernel] " Julia Lawall
2016-09-16 9:58 ` Gargi Sharma
2016-09-16 10:07 ` Julia Lawall
2016-09-16 2:46 ` [PATCH 6/8] staging: wlan-ng: delete space after a cast Gargi Sharma
2016-09-16 5:37 ` [Outreachy kernel] " Julia Lawall
2016-09-16 2:46 ` [PATCH 7/8] staging: wlan-ng: add blank line after declaration Gargi Sharma
2016-09-16 5:35 ` [Outreachy kernel] " Julia Lawall
2016-09-16 2:46 ` [PATCH 8/8] staging: wlan-ng: fix block comment style Gargi Sharma
2016-09-16 5:33 ` [Outreachy kernel] " Julia Lawall
2016-09-16 5:40 ` Alison Schofield
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.1473993585.git.gs051095@gmail.com \
--to=gs051095@gmail.com \
--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.