From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging wlan-ng: Add missing blank lines after declarations
Date: Wed, 17 Sep 2014 05:52:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1409170549530.25841@localhost> (raw)
In-Reply-To: <1410921717-16195-1-git-send-email-xerofoify@gmail.com>
On Tue, 16 Sep 2014, Nicholas Krause wrote:
> Fixing trivial checkpatch warnings about missing blank lines after declarations.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
... snip ...
>From Documentation/SubmittingPatches:
"The "summary phrase" may be prefixed by tags enclosed in square
brackets: "Subject: [PATCH tag] <summary phrase>". The tags are not
considered part of the summary phrase, but describe how the patch
should be treated. Common tags might include a version descriptor if
the multiple versions of the patch have been sent out in response to
comments (i.e., "v1, v2, v3") ..."
this is now ... what? version 6? 7? 8? of a patch that adds three
blank lines to a file. so ... still wrong.
didn't you say you were going to leave if you couldn't submit the
next patch properly? whatever happened to that promise?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-09-17 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 2:41 [PATCH] staging wlan-ng: Add missing blank lines after declarations Nicholas Krause
2014-09-17 2:44 ` nick
2014-09-17 9:52 ` Robert P. J. Day [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-16 21:58 Nicholas Krause
2014-09-16 21:59 ` nick
2014-09-17 1:26 ` Amit Agarwal
2014-09-16 21:30 Nicholas Krause
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=alpine.LFD.2.11.1409170549530.25841@localhost \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).