The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ziran Zhang <zhangcoder@yeah.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
	Neal Cardwell <ncardwell@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Simon Horman <horms@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Ziran Zhang <zhangcoder@yeah.net>
Subject: Re: [PATCH net-next] tcp: fix mdev comment in tcp_rtt_estimator()
Date: Tue, 18 Aug 2026 23:42:53 +0800	[thread overview]
Message-ID: <20260818154253.6895-1-zhangcoder@yeah.net> (raw)
In-Reply-To: <20260818081346.03773154@kernel.org>

On Tue, 18 Aug 2026 08:13:46 -0700 Jakub Kicinski wrote:
> ## Form letter - net-next-closed
> 
> The merge window for v7.3 has started, and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations.
> We will only consider applying net-next patches which were posted
> before the announcement:
> 
> https://lore.kernel.org/20260816155953.072d73da@kernel.org
> 
> Fixes are obviously welcome at any time. net-next patches may be sent
> for review and discussion only with an RFC tag.
> 
> Please repost when net-next reopens.
> 
> See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
> -- 
> pw-bot: defer
> pv-bot: closed

Hi Jakub,

Thanks for your reply.

I understand that net-next is currently closed. I will wait for it to reopen 
and then resubmit the patch.

Thanks,
Ziran Zhang


  reply	other threads:[~2026-08-18 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  8:51 [PATCH net-next] tcp: fix mdev comment in tcp_rtt_estimator() Ziran Zhang
2026-08-18 15:13 ` Jakub Kicinski
2026-08-18 15:42   ` Ziran Zhang [this message]
2026-08-18 15:53     ` Jakub Kicinski
2026-08-18 16:03       ` Ziran Zhang

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=20260818154253.6895-1-zhangcoder@yeah.net \
    --to=zhangcoder@yeah.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncardwell@google.com \
    --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