netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Angus Chen <angus.chen@jaguarmicro.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: Remove low_thresh in ip defrag
Date: Mon, 15 May 2023 07:50:25 +0000	[thread overview]
Message-ID: <168413702530.26935.9409301901790238640.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512010152.1602-1-angus.chen@jaguarmicro.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 12 May 2023 09:01:52 +0800 you wrote:
> As low_thresh has no work in fragment reassembles,del it.
> And Mark it deprecated in sysctl Document.
> 
> Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
> ---
> 
> v2:
>  Fix some spelling errors,and remove low_thresh from struct fqdir.
>  suggested by Jakub Kicinski <kuba@kernel.org>.
> 
> [...]

Here is the summary with links:
  - [v2] net: Remove low_thresh in ip defrag
    https://git.kernel.org/netdev/net-next/c/b2cbac9b9b28

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2023-05-15  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  1:01 [PATCH v2] net: Remove low_thresh in ip defrag Angus Chen
2023-05-15  7:50 ` patchwork-bot+netdevbpf [this message]
2023-05-15 11:02 ` Ido Schimmel
2023-05-15 12:06   ` Angus Chen
2023-05-16  8:12     ` Ido Schimmel
2023-05-16  8:36       ` Angus Chen
2023-05-15 12:46 ` Petr Machata

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=168413702530.26935.9409301901790238640.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=angus.chen@jaguarmicro.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --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).