From: Joe Perches <joe@perches.com>
To: Luis de Bethencourt <luis@debethencourt.com>
Cc: linux-kernel@vger.kernel.org, jarod@wilsonet.com,
m.chehab@samsung.com, gregkh@linuxfoundation.org,
mahfouz.saif.elyazal@gmail.com, dan.carpenter@oracle.com,
tuomas.tynkkynen@iki.fi, gulsah.1004@gmail.com,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: media: lirc: lirc_zilog.c: fix quoted strings split across lines
Date: Tue, 25 Nov 2014 17:49:40 -0800 [thread overview]
Message-ID: <1416966580.8358.17.camel@perches.com> (raw)
In-Reply-To: <20141125211428.GA12346@biggie>
On Tue, 2014-11-25 at 21:14 +0000, Luis de Bethencourt wrote:
> On Tue, Nov 25, 2014 at 01:00:07PM -0800, Joe Perches wrote:
> > In the future, you might consider being more
> > comprehensive with your patches.
>
> Wasn't sure about the scope of the style fixing
> patches. I've been reading Kernel Newbies and
> this looked like a good way to start
> contributing. Good to know more exhaustive
> changes are welcome.
> >
> > This code could be neatened a bit by:
> >
> > o using another set of logging macros
> > o removing the unnecessary ftrace like logging
> > o realigning arguments
>
> Great ideas.
> Should this have been all included in one patch,
> or each as part of a series with the previous
> one?
> Want to take the opportunity to learn about the
> process.
Hello again Luis.
I think the suggestion I posted here is suitable
for a single change.
Ideally, you'd make individual patches each with
a single "type" of change.
There is a script I posted a while back that
groups various checkpatch "types" together and
makes it a bit easier to do cleanup style
patches.
https://lkml.org/lkml/2014/7/11/794
But don't just use checkpatch as the sole
decider of what's appropriate to fix or neaten.
checkpatch is a stupid, brainless little script.
So is the automation script that uses checkpatch.
For instance, checkpatch would not have suggested
creating and using another logging macro.
Please use your own taste to best figure out what
to fix and how.
Using checkpatch to get familiar with kernel
development is fine and all, but fixing actual
defects and submitting new code is way more
useful.
cheers, welcome, Joe
next prev parent reply other threads:[~2014-11-26 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 20:19 [PATCH] staging: media: lirc: lirc_zilog.c: fix quoted strings split across lines Luis de Bethencourt
2014-11-25 20:27 ` Joe Perches
2014-11-25 20:40 ` Luis de Bethencourt
2014-11-25 21:00 ` Joe Perches
2014-11-25 21:14 ` Luis de Bethencourt
2014-11-26 1:49 ` Joe Perches [this message]
[not found] ` <CAPA4HGVJ_gJacLtgtQSJgSjgks9_7aGSuy2+aLOtkz01+Ng7CQ@mail.gmail.com>
2014-11-26 16:05 ` Joe Perches
2014-11-27 0:39 ` Luis de Bethencourt
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=1416966580.8358.17.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=gulsah.1004@gmail.com \
--cc=jarod@wilsonet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luis@debethencourt.com \
--cc=m.chehab@samsung.com \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=tuomas.tynkkynen@iki.fi \
/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