[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171222103026.75dac65c358eea12ffbb3ae5@kernel.org>
Date: Fri, 22 Dec 2017 10:30:26 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: David Miller <davem@...emloft.net>, mhiramat@...nel.org,
mingo@...nel.org, ian.mcdonald@...di.co.nz, vyasevich@...il.com,
stephen@...workplumber.org, peterz@...radead.org,
tglx@...utronix.de, linux-kernel@...r.kernel.org, hpa@...or.com,
gerrit@....abdn.ac.uk, nhorman@...driver.com, dccp@...r.kernel.org,
netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
sfr@...b.auug.org.au
Subject: Re: [PATCH net-next v4.1 5/6] net: dccp: Add DCCP sendmsg trace
event
On Thu, 21 Dec 2017 11:08:05 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 21 Dec 2017 10:57:36 -0500 (EST)
> David Miller <davem@...emloft.net> wrote:
>
> > When you fix any part of a patch series, you must always repost the
> > entire series from scratch, not just the patch(s) that change.
>
> He probably gets that from me. I don't usually require a full series if
> only a single patch changes. But I don't receive as many patch series
> as you do, so I can handle that work flow without too much difficulty.
Yeah :)
OK, anyway, this is for net-next branch. I follow that rule.
I'm happy to resend the series :)
Thank you,
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists