From: Greg KH <gregkh@linuxfoundation.org>
To: Evan Ng <evan.sin.ng@gmail.com>
Cc: pe1dnn@amsat.org, johanmeiring@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlags49_h2: fixed 80 line character and white space issue in ap_h2.c Fixed various coding style warnings found by the checkpatch.pl tool
Date: Fri, 2 Aug 2013 06:28:40 +0800 [thread overview]
Message-ID: <20130801222840.GA5444@kroah.com> (raw)
In-Reply-To: <CAGkkOHezKfjYaGJHcbPPiE4EobOLMp=K62-NWhpbvp2QDhLOfA@mail.gmail.com>
On Thu, Aug 01, 2013 at 03:08:21PM -0700, Evan Ng wrote:
> Thanks for the reply,
>
> Being this is my first patch that I have submitted, I want to clarify a few
> things:
>
> My *corrected* subject should read something like this?
>
> "Subject: [PATCH] Staging: wlags49_h2: fixed 80 line character and white space
> issue in ap_h2.c Fixed various coding style warnings found by
> the
> checkpatch.pl tool
> \n
> LONGER DESCRIPTION GOES HERE"
No.
It should be:
Subject: [PATCH] Staging: wlags48_h2: ap_h2.c: fixed tab whitespace issue
This patch fixes the tab vs. spaces white space issues in this
file.
Signed-off-by: ....
> As for the doing "one thing at a time" would it be preferred if I fix the
> syntax of one function within a file a time? Would that mean that for one
> simple .c file I could be making 15 or so commits to it?
How about fixing one specific warning at a time for the whole file?
Like tab issues, and then { issues, and then ' ' issues, and so on. See
the archives of the mailing list for lots of examples of how to do this
properly.
hope this helps,
greg k-h
next prev parent reply other threads:[~2013-08-01 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375303465-3437-1-git-send-email-evan.sin.ng@gmail.com>
2013-08-01 21:50 ` [PATCH] Staging: wlags49_h2: fixed 80 line character and white space issue in ap_h2.c Fixed various coding style warnings found by the checkpatch.pl tool Greg KH
[not found] ` <CAGkkOHezKfjYaGJHcbPPiE4EobOLMp=K62-NWhpbvp2QDhLOfA@mail.gmail.com>
2013-08-01 22:28 ` Greg KH [this message]
2013-08-01 23:48 ` Joe Perches
2013-08-02 10:37 ` Dan Carpenter
2013-08-02 19:39 ` Evan Ng
2013-08-04 15:43 ` Henk de Groot
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=20130801222840.GA5444@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=evan.sin.ng@gmail.com \
--cc=johanmeiring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pe1dnn@amsat.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.