From: David Miller <davem@davemloft.net>
To: laoar.shao@gmail.com
Cc: songliubraving@fb.com, marcelo.leitner@gmail.com,
rostedt@goodmis.org, bgregg@netflix.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/4] replace tcp_set_state tracepoint with
Date: Fri, 15 Dec 2017 12:51:46 -0500 (EST) [thread overview]
Message-ID: <20171215.125146.2083491338570871230.davem@davemloft.net> (raw)
In-Reply-To: <CALOAHbB_T4A4mK6RW0Rw3KTjoDTwj-KZ048kS-qPUeFShBWU_g@mail.gmail.com>
From: Yafang Shao <laoar.shao@gmail.com>
Date: Sat, 16 Dec 2017 01:50:12 +0800
> 2017-12-16 1:43 GMT+08:00 David Miller <davem@davemloft.net>:
>>
>> Your Subject line here is incomplete, "replace tcp_set_state
>> tracepoint with" what?
>
> Oh Sorry.
>
> The subject should be
>
> "replace tcp_set_state tracepoint with sock_set_state tracepoint"
Please resubmit with it fixed.
prev parent reply other threads:[~2017-12-15 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 17:01 Yafang Shao
2017-12-15 17:01 ` [PATCH v2 net-next 1/4] tcp: Export to userspace the TCP state names for the trace events Yafang Shao
2017-12-15 17:01 ` [PATCH v2 net-next 2/4] net: tracepoint: replace tcp_set_state tracepoint with sock_set_state tracepoint Yafang Shao
2017-12-15 17:01 ` [PATCH v2 net-next 3/4] net: tracepoint: using sock_set_state tracepoint to trace DCCP state transition Yafang Shao
2017-12-15 17:01 ` [PATCH v2 net-next 4/4] net: tracepoint: using sock_set_state tracepoint to trace SCTP " Yafang Shao
2017-12-15 17:43 ` [PATCH v2 net-next 0/4] replace tcp_set_state tracepoint with David Miller
2017-12-15 17:50 ` Yafang Shao
2017-12-15 17:51 ` David Miller [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=20171215.125146.2083491338570871230.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bgregg@netflix.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.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
all inboxes | Powered by JetHome®