From: Jakub Kicinski <kuba@kernel.org>
To: Angus Chen <angus.chen@jaguarmicro.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: Remove low_thresh in ip defrag
Date: Wed, 10 May 2023 18:33:57 -0700 [thread overview]
Message-ID: <20230510183357.1b8501fd@kernel.org> (raw)
In-Reply-To: <20230509071243.1572-1-angus.chen@jaguarmicro.com>
On Tue, 9 May 2023 15:12:43 +0800 Angus Chen wrote:
> As low_thresh has no work in fragment reassembles,del it.
You're not really deleting it.
Please use spellcheck.
You also misspelled "unused" in the code.
--
pw-bot: cr
next prev parent reply other threads:[~2023-05-11 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 7:12 [PATCH] net: Remove low_thresh in ip defrag Angus Chen
2023-05-11 1:33 ` Jakub Kicinski [this message]
2023-05-12 1:00 ` Angus Chen
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=20230510183357.1b8501fd@kernel.org \
--to=kuba@kernel.org \
--cc=angus.chen@jaguarmicro.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).