From: Joe Perches <joe@perches.com>
To: Giuliano Belinassi <giuliano.belinassi@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: ad7280a: Lines should not end with a '(' - style
Date: Tue, 16 Oct 2018 16:07:58 -0700 [thread overview]
Message-ID: <d00fec12b481f17ce6e844d86be56b5f12bdb0b1.camel@perches.com> (raw)
In-Reply-To: <CAG4RSAFMGSFyUqutRD2SRMsBt5RHVo5RUQsBq7fis6OVWxSZbg@mail.gmail.com>
(There is a linux-usp@googlegroups.com mailing list
that bounces when I reply, so I removed it from the
cc list)
On Tue, 2018-10-16 at 19:48 -0300, Giuliano Belinassi wrote:
> Hello,
> Thank you for your review :-).
> Sorry, but I am a newbie on this, and now I am confused about my next
> step. Should I make a v2 based on your changes, or do you want to submit
> your changes?
I wrote that to encourage you to do more than
what checkpatch says.
I just moved code around and reduced duplication.
There are many similar opportunities for code
refactoring in staging.
You could test what I wrote, add a good commit
message with a subject like:
[PATCH V2] staging: iio: ad7280a: Refactor <functionname>
with a commit message that describes the changes and
perhaps shows the object size difference using
$ size <old> <new>
Maybe add a Suggested-by: tag if it pleases you, but
what I did is trivial and I think it's unnecessary.
Are you doing this for a class assignment?
next prev parent reply other threads:[~2018-10-16 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 21:09 Giuliano Belinassi
2018-10-16 21:59 ` Joe Perches
[not found] ` <CAG4RSAFMGSFyUqutRD2SRMsBt5RHVo5RUQsBq7fis6OVWxSZbg@mail.gmail.com>
2018-10-16 23:07 ` Joe Perches [this message]
2018-10-16 23:29 ` Giuliano Augusto Faulin Belinassi
2018-10-16 23:57 ` Joe Perches
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=d00fec12b481f17ce6e844d86be56b5f12bdb0b1.camel@perches.com \
--to=joe@perches.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=giuliano.belinassi@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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
all inboxes | Powered by JetHome®