From: Maksymilian Piechota <maksymilianpiechota@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, maksymilian.piechota@gmail.com,
linux-kernel@vger.kernel.org
Subject: [PATCHv6 0/3] staging: wlan-ng: align else if statement to coding standard
Date: Mon, 13 Feb 2017 09:21:57 -0500 [thread overview]
Message-ID: <cover.1486993631.git.maksymilianpiechota@gmail.com> (raw)
PATCHv0:
- Spaces replaced with tabs
Maksymilian Piechota (1):
staging: wlan-ng: This patch fixes the checkpatch.pl warning:
else if statement still did not fulfill coding standard requirements.
PATCHv2:
- else if statement moved to single line
Maksymilian Piechota (1):
staging: wlan-ng: This patch fixes the checkpatch.pl warning:
Subject was not precise.
PATCHv3:
- Subject is more precise
- Changelog text describe every change
Maksymilian Piechota (1):
staging: lustre: align else if statement to coding standard
Too much changes for one patch.
PATCHv4:
- Previous patch breaked up to particular patches for every change
Maksymilian Piechota (2):
staging: lustre: move logical continuations at the end of line
staging: lustre: move else if statement to a single line
Continuation of the statement should be realigned
PATCHv5:
- Wrong prefixes in commits and patches titles changed
- Else if continuation realigned
Maksymilian Piechota (3):
staging: wlan-ng: move logical continuations at the end of line
staging: wlan-ng: move else if statement to a single line
staging: wlan-ng: realign else if continuation
Lack of patches history. No changelog text for particular patches
PATCHv6:
- changelog text for patches added
- patches history added
Maksymilian Piechota (3):
staging: wlan-ng: move logical continuations at the end of line
staging: wlan-ng: move else if statement to a single line
staging: wlan-ng: realign else if continuation
drivers/staging/wlan-ng/prism2mgmt.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--
2.1.4
next reply other threads:[~2017-02-13 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 14:21 Maksymilian Piechota [this message]
2017-02-13 14:25 ` [PATCHv6 1/3] staging: wlan-ng: move logical continuations at the end of line Maksymilian Piechota
2017-02-14 17:16 ` Greg Kroah-Hartman
2017-02-15 11:53 ` Maksymilian Piechota
2017-02-15 14:26 ` Greg Kroah-Hartman
2017-02-13 14:30 ` [PATCHv6 2/3] staging: wlan-ng: move else if statement to a single line Maksymilian Piechota
2017-02-13 14:32 ` [PATCHv6 3/3] staging: wlan-ng: realign else if continuation Maksymilian Piechota
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.1486993631.git.maksymilianpiechota@gmail.com \
--to=maksymilianpiechota@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maksymilian.piechota@gmail.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