From: Steven Rostedt <rostedt@goodmis.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: xu.xin16@zte.com.cn, edumazet@google.com, davem@davemloft.net,
mhiramat@kernel.org, dsahern@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
netdev@vger.kernel.org, yang.yang29@zte.com.cn,
he.peilin@zte.com.cn, liu.chun2@zte.com.cn,
jiang.xuexin@zte.com.cn, zhang.yunkai@zte.com.cn
Subject: Re: [PATCH v3] net/ipv4: add tracepoint for icmp_send
Date: Thu, 21 Mar 2024 09:39:04 -0400 [thread overview]
Message-ID: <20240321093904.65f91d10@gandalf.local.home> (raw)
In-Reply-To: <CAL+tcoAdZOKnHTbRnmrjtrhJynGfDy4xXvus1hh_UTbh5eSMTA@mail.gmail.com>
On Thu, 21 Mar 2024 10:45:00 +0800
Jason Xing <kerneljasonxing@gmail.com> wrote:
> The format of the whole patch looks strange... Did you send this patch
> by using 'git send-email' instead of pasting the text and sending?
Yeah, it's uuencoded.
Subject: =?UTF-8?B?wqBbUEFUQ0ggdjNdIG5ldC9pcHY0OiBhZGQgdHJhY2Vwb2ludCBmb3IgaWNtcF9zZW5k?=
Content-Type: multipart/mixed;
boundary="=====_001_next====="
X-MAIL:mse-fl2.zte.com.cn 42L2Ahm2097008
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 65FB975E.000/4V0TV60kJlz8XrRb
--=====_001_next=====
Content-Type: multipart/related;
boundary="=====_002_next====="
--=====_002_next=====
Content-Type: multipart/alternative;
boundary="=====_003_next====="
--=====_003_next=====
Content-Type: text/plain;
charset="UTF-8"
Content-Transfer-Encoding: base64
-- Steve
next prev parent reply other threads:[~2024-03-21 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 2:10 [PATCH v3] net/ipv4: add tracepoint for icmp_send xu.xin16
2024-03-21 2:45 ` Jason Xing
2024-03-21 13:39 ` Steven Rostedt [this message]
2024-03-22 7:41 ` Denis Kirjanov
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=20240321093904.65f91d10@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=he.peilin@zte.com.cn \
--cc=jiang.xuexin@zte.com.cn \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=liu.chun2@zte.com.cn \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=zhang.yunkai@zte.com.cn \
/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