From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: wenxu@ucloud.cn
Cc: kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next 2/2] net/sched: act_frag: add implict packet fragment support.
Date: Fri, 6 Nov 2020 05:56:40 -0300 [thread overview]
Message-ID: <20201106085640.GA3913@localhost.localdomain> (raw)
In-Reply-To: <1604572893-16156-2-git-send-email-wenxu@ucloud.cn>
On Thu, Nov 05, 2020 at 06:41:33PM +0800, wenxu@ucloud.cn wrote:
> From: wenxu <wenxu@ucloud.cn>
I see Davide's and Jakub's comments. Other than those, I don't have
further comments. LGTM!
prev parent reply other threads:[~2020-11-06 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:41 [PATCH v3 net-next 1/2] net/sched: act_mirred: refactor the handle of xmit wenxu
2020-11-05 10:41 ` [PATCH v3 net-next 2/2] net/sched: act_frag: add implict packet fragment support wenxu
2020-11-05 11:03 ` Davide Caratti
2020-11-05 22:19 ` Jakub Kicinski
2020-11-06 8:56 ` Marcelo Ricardo Leitner [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=20201106085640.GA3913@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wenxu@ucloud.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;
as well as URLs for NNTP newsgroup(s).