From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: David Miller <davem@davemloft.net>,
mhiramat@kernel.org, mingo@kernel.org, ian.mcdonald@jandi.co.nz,
vyasevich@gmail.com, stephen@networkplumber.org,
peterz@infradead.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, hpa@zytor.com,
gerrit@erg.abdn.ac.uk, nhorman@tuxdriver.com,
dccp@vger.kernel.org, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH net-next v4.1 5/6] net: dccp: Add DCCP sendmsg trace event
Date: Fri, 22 Dec 2017 10:30:26 +0900 [thread overview]
Message-ID: <20171222103026.75dac65c358eea12ffbb3ae5@kernel.org> (raw)
In-Reply-To: <20171221110805.37931c4d@gandalf.local.home>
On Thu, 21 Dec 2017 11:08:05 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 21 Dec 2017 10:57:36 -0500 (EST)
> David Miller <davem@davemloft.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@kernel.org>
next prev parent reply other threads:[~2017-12-22 1:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 4:14 [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events Masami Hiramatsu
2017-12-20 4:14 ` [PATCH net-next v4 1/6] net: tcp: Add trace events for TCP congestion window tracing Masami Hiramatsu
2017-12-20 4:15 ` [PATCH net-next v4 2/6] net: tcp: Remove TCP probe module Masami Hiramatsu
2017-12-20 4:15 ` [PATCH net-next v4 3/6] net: sctp: Add SCTP ACK tracking trace event Masami Hiramatsu
2017-12-20 4:16 ` [PATCH net-next v4 4/6] net: sctp: Remove debug SCTP probe module Masami Hiramatsu
2017-12-20 4:16 ` [PATCH net-next v4 5/6] net: dccp: Add DCCP sendmsg trace event Masami Hiramatsu
2017-12-21 14:43 ` [PATCH net-next v4.1 " Masami Hiramatsu
2017-12-21 15:57 ` David Miller
2017-12-21 16:08 ` Steven Rostedt
2017-12-22 1:30 ` Masami Hiramatsu [this message]
2017-12-20 4:17 ` [PATCH net-next v4 6/6] net: dccp: Remove dccpprobe module Masami Hiramatsu
2017-12-20 19:20 ` [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events David Miller
2017-12-20 19:24 ` David Miller
2017-12-21 0:10 ` Masami Hiramatsu
2017-12-21 2:36 ` Masami Hiramatsu
2017-12-21 3:12 ` Steven Rostedt
2017-12-21 13:16 ` Masami Hiramatsu
2017-12-21 14:27 ` Masami Hiramatsu
2017-12-21 4:08 ` David Miller
2017-12-21 12:43 ` Masami Hiramatsu
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=20171222103026.75dac65c358eea12ffbb3ae5@kernel.org \
--to=mhiramat@kernel.org \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=gerrit@erg.abdn.ac.uk \
--cc=hpa@zytor.com \
--cc=ian.mcdonald@jandi.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=vyasevich@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 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).