From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Checkpatch Patches
Date: Tue, 16 Sep 2014 15:30:37 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1409161528560.17832@localhost> (raw)
In-Reply-To: <5418851E.3040104@surriel.com>
On Tue, 16 Sep 2014, Rik van Riel wrote:
> Nick,
>
> this is a chance for you to prove the nay-sayers wrong (or right).
>
> When re-posting your patch, you can include information on what tips
> you got on how to improve the patch, and how you applied that
> information in the new version of the patch.
>
> This is a good idea for anybody resubmitting a changed patch,
> because it tells other reviewers what changes were made, why, and
> who pointed out the idea for the change.
my god, rik, you're adorable. :-) i predict that, despite what i've
posted *twice*, nick will describe as an "error" what is simply a
checkpatch coding style *warning*. let's watch ...
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-16 19:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 12:44 Checkpatch Patches nick
2014-09-16 12:47 ` Kristofer Hallin
2014-09-16 12:50 ` nick
2014-09-16 13:06 ` Sudip Mukherjee
2014-09-16 13:11 ` nick
2014-09-16 13:21 ` Sudip Mukherjee
2014-09-16 13:26 ` nick
[not found] ` <CADVatmOZx7q636=b0pQ95CZ93_6jn_jZ2SCPKH7pHmw9P0mRuQ@mail.gmail.com>
[not found] ` <54183C0A.80409@gmail.com>
[not found] ` <CADVatmP1G1pg-vDmn1z-vg9Ppn7Yhvc=hnhbaOyENbdg6WUO2A@mail.gmail.com>
2014-09-16 13:47 ` Sudip Mukherjee
2014-09-16 13:07 ` Robert P. J. Day
2014-09-16 13:13 ` Robert P. J. Day
2014-09-16 14:19 ` Valdis.Kletnieks at vt.edu
2014-09-16 15:44 ` Nick Krause
2014-09-16 15:50 ` Carlo Caione
2014-09-16 15:57 ` Lidza Louina
2014-09-16 16:08 ` Valdis.Kletnieks at vt.edu
2014-09-16 16:14 ` Robert P. J. Day
2014-09-16 16:11 ` Robert P. J. Day
2014-09-16 16:10 ` Hugo Mills
2014-09-16 16:57 ` Sudip Mukherjee
2014-09-16 17:12 ` Nick Krause
2014-09-16 17:27 ` Robert P. J. Day
2014-09-16 17:27 ` Valdis.Kletnieks at vt.edu
2014-09-16 17:28 ` Rik van Riel
2014-09-16 17:39 ` Valdis.Kletnieks at vt.edu
2014-09-16 18:29 ` Nick Krause
2014-09-16 18:36 ` Kristofer Hallin
2014-09-16 18:44 ` Rik van Riel
2014-09-16 19:30 ` Robert P. J. Day [this message]
2014-09-16 18:45 ` Mandeep Sandhu
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.1409161528560.17832@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 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.