From: Peter Hurley <peter@hurleysoftware.com>
To: domdevlin@free.fr
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shraddha Barke <shraddha.6596@gmail.com>,
Radek Dostal <rd@radekdostal.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] staging: fwserial: (coding style) Rewriting a call to a long function
Date: Fri, 1 Apr 2016 16:29:45 -0700 [thread overview]
Message-ID: <56FF0469.7000400@hurleysoftware.com> (raw)
In-Reply-To: <1459552801.5550.15.camel@free.fr>
On 04/01/2016 04:20 PM, Dominique van den Broeck wrote:
> Hello Peter,
> Thanks a lot for your review and kind advice !
>
>> I don't see a > 80-col line here?
>
> In fact, it was not even a 80-col issue but a mis-aligned parenthesis
> one. Realign the rows in this state would make them exceed the 80th
> column.
Ah, ok. Wasn't clear from the commit message.
> I tend to agree with the fact that the way it currently is remains the
> best one.
Ok.
>> And even if I did, this change would be super-ugly.
>> The preferred way to reduce this is to fold it into a helper
>> function
>
> Actually, before I resend my patches, I have two or three small
> questions:
>
> 1) My v1 patches already made it to staging and linux-next trees.
> Should I resend them anyway ?
No, I didn't know they were already in staging-next.
Nevermind then :)
> 2) Would it be helpful to people if I write a function the way you
> specified it or would it be better to let it as is ?
As is, please.
> 3) If we don't, and then discard the last patch, shall I number « n/2 »
> or « n/3 » anyway ?
n/a now.
> Forgive me if these questions are lame, I still have only a few
> experience of the kernel tree.
Your questions are not lame; no need to apologize.
> Documentation/SubmittingPatches states
> that no one should be expected to refer to a previous set of patches,
> so I suppose this would be « 1/2 » and « 2/2 » but I prefer being OK
> about this from the beginning.
If you would have sent the patches, yes, they would have been 1/2 and 2/2.
What I do there is send the v2 series in-reply-to the original 1/2 patch.
> Thanks for caring.
Regards,
Peter Hurley
next prev parent reply other threads:[~2016-04-01 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 17:14 [PATCH 1/3] staging: fwserial: (coding style) Turning every "unsigned" into "unsigned int" Dominique van den Broeck
2016-03-29 17:14 ` [PATCH 2/3] staging: fwserial: (coding style) removing "!= NULL" to comply with checkpatch.pl Dominique van den Broeck
2016-04-01 16:25 ` Peter Hurley
2016-03-29 17:14 ` [PATCH 3/3] staging: fwserial: (coding style) Rewriting a call to a long function Dominique van den Broeck
2016-03-29 17:38 ` Joe Perches
2016-03-29 17:50 ` Dominique van den Broeck
2016-04-01 16:38 ` Peter Hurley
2016-04-01 23:20 ` Dominique van den Broeck
2016-04-01 23:29 ` Peter Hurley [this message]
2016-04-01 16:22 ` [PATCH 1/3] staging: fwserial: (coding style) Turning every "unsigned" into "unsigned int" Peter Hurley
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=56FF0469.7000400@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=domdevlin@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rd@radekdostal.com \
--cc=shraddha.6596@gmail.com \
/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.