From: Gerlando Falauto <gerlando.falauto@keymile.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sergei.shtylyov@cogentembedded.com"
<sergei.shtylyov@cogentembedded.com>,
"jon.maloy@ericsson.com" <jon.maloy@ericsson.com>,
"erik.hugne@ericsson.com" <erik.hugne@ericsson.com>,
"ying.xue@windriver.com" <ying.xue@windriver.com>,
"Brunck, Holger" <Holger.Brunck@keymile.com>
Subject: Re: [PATCH v3b 1/3] tipc: cosmetic: clean up comments and break a long line
Date: Wed, 01 May 2013 19:56:30 +0200 [thread overview]
Message-ID: <5181574E.8060909@keymile.com> (raw)
In-Reply-To: <20130501.134356.491039302692790983.davem@davemloft.net>
Hi,
On 05/01/2013 07:43 PM, David Miller wrote:
> From: Gerlando Falauto <gerlando.falauto@keymile.com>
> Date: Wed, 01 May 2013 19:35:09 +0200
>
>> That I don't understand. I thought it would be the other way around,
>> that's why I resubmitted only the one which changed.
>
> Any patch you submit I assume you test applied yourself successfully,
> therefore by submitting it you are saying that you validated them
> as a series explicitly or know that the other patches have no conflicts.
I understand, you're right. I hope adding "Changes from v(n-1): None"
should also be enough to say that further review should not be necessary
as the patch is identical to the previous version.
> Also, please never submit new versions of patches in replies to older
> patch discussions.
>
> Chain replies in order to construct a series are OK, especially when
> you provide a proper "[PATCH 0/N] ..." initial posting explaining
> the series.
>
OK, thanks.
Gerlando
prev parent reply other threads:[~2013-05-01 17:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 14:13 [PATCH v2 1/2] tipc: tipc_bcbearer_send(): simplify bearer selection Gerlando Falauto
2013-04-29 14:13 ` [PATCH v2 2/2] tipc: pskb_copy() buffers when sending on more than one bearer Gerlando Falauto
2013-04-29 19:45 ` David Miller
2013-04-29 19:44 ` [PATCH v2 1/2] tipc: tipc_bcbearer_send(): simplify bearer selection David Miller
2013-04-30 7:33 ` [PATCH v3 1/3] tipc: cosmetic: clean up comments Gerlando Falauto
2013-04-30 7:33 ` [PATCH v3 2/3] tipc: tipc_bcbearer_send(): simplify bearer selection Gerlando Falauto
2013-04-30 7:33 ` [PATCH v3 3/3] tipc: pskb_copy() buffers when sending on more than one bearer Gerlando Falauto
2013-04-30 11:54 ` [PATCH v3 1/3] tipc: cosmetic: clean up comments Sergei Shtylyov
2013-04-30 19:07 ` David Miller
2013-05-01 7:37 ` Gerlando Falauto
2013-05-01 16:18 ` Sergei Shtylyov
2013-05-01 16:41 ` [PATCH v3b 1/3] tipc: cosmetic: clean up comments and break a long line Gerlando Falauto
2013-05-01 17:16 ` David Miller
2013-05-01 17:35 ` Gerlando Falauto
2013-05-01 17:43 ` David Miller
2013-05-01 17:56 ` Gerlando Falauto [this message]
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=5181574E.8060909@keymile.com \
--to=gerlando.falauto@keymile.com \
--cc=Holger.Brunck@keymile.com \
--cc=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ying.xue@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).