public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: chia-yu.chang@nokia-bell-labs•com
Cc: tariqt@nvidia•com, linux-rdma@vger•kernel.org,
	shaojijie@huawei•com, shenjian15@huawei•com,
	salil.mehta@huawei•com, mbloch@nvidia•com, saeedm@nvidia•com,
	leon@kernel•org, eperezma@redhat•com, brett.creeley@amd•com,
	jasowang@redhat•com, virtualization@lists•linux.dev,
	mst@redhat•com, xuanzhuo@linux•alibaba.com, pabeni@redhat•com,
	edumazet@google•com, parav@nvidia•com, linux-doc@vger•kernel.org,
	corbet@lwn•net, horms@kernel•org, dsahern@kernel•org,
	kuniyu@google•com, bpf@vger•kernel.org, netdev@vger•kernel.org,
	dave.taht@gmail•com, jhs@mojatatu•com,
	stephen@networkplumber•org, xiyou.wangcong@gmail•com,
	jiri@resnulli•us, davem@davemloft•net, andrew+netdev@lunn•ch,
	donald.hunter@gmail•com, ast@fiberby•net, liuhangbin@gmail•com,
	shuah@kernel•org, linux-kselftest@vger•kernel.org, ij@kernel•org,
	ncardwell@google•com, koen.de_schepper@nokia-bell-labs•com,
	g.white@cablelabs•com, ingemar.s.johansson@ericsson•com,
	mirja.kuehlewind@ericsson•com, cheshire@apple•com,
	rs.ietf@gmx•at, Jason_Livingood@comcast•com,
	vidhi_goel@apple•com
Subject: Re: [PATCH v1 net-next 0/3] ECN offload handling for AccECN series
Date: Sat, 31 Jan 2026 16:45:16 -0800	[thread overview]
Message-ID: <20260131164516.4a423230@kernel.org> (raw)
In-Reply-To: <20260131225510.2946-1-chia-yu.chang@nokia-bell-labs.com>

On Sat, 31 Jan 2026 23:55:07 +0100 chia-yu.chang@nokia-bell-labs•com
wrote:
> ---
> v2:
> - Replace VIRTIO_NET_HDR_GSO_ECN with VIRTIO_NET_HDR_GSO_ECN_FLAGS

For the future:

Quoting documentation:

  Limit patches outstanding on mailing list
  -----------------------------------------
  
  Avoid having more than 15 patches, across all series, outstanding for
  review on the mailing list for a single tree. In other words, a maximum of
  15 patches under review on net, and a maximum of 15 patches under review on
  net-next.
  
  This limit is intended to focus developer effort on testing patches before
  upstream review. Aiding the quality of upstream submissions, and easing the
  load on reviewers.
    
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#limit-patches-outstanding-on-mailing-list

  parent reply	other threads:[~2026-02-01  0:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 22:55 [PATCH v1 net-next 0/3] ECN offload handling for AccECN series chia-yu.chang
2026-01-31 22:55 ` [PATCH v1 net-next 1/3] net: update commnets for SKB_GSO_TCP_ECN and SKB_GSO_TCP_ACCECN chia-yu.chang
2026-02-01  9:01   ` Michael S. Tsirkin
2026-01-31 22:55 ` [PATCH v1 net-next 2/3] net: hns3/mlx5e: avoid corrupting CWR flag when receiving GRO packet chia-yu.chang
2026-02-01  9:05   ` Michael S. Tsirkin
2026-02-02 16:44     ` Chia-Yu Chang (Nokia)
2026-01-31 22:55 ` [PATCH v1 net-next 3/3] virtio_net: Accurate ECN flag in virtio_net_hdr chia-yu.chang
2026-02-01  9:17   ` Michael S. Tsirkin
2026-02-02 16:56     ` Chia-Yu Chang (Nokia)
2026-02-02 17:19       ` Michael S. Tsirkin
2026-02-02 21:09         ` Chia-Yu Chang (Nokia)
2026-02-02 23:45           ` Michael S. Tsirkin
2026-02-01  0:45 ` Jakub Kicinski [this message]
2026-02-02 14:10   ` [PATCH v1 net-next 0/3] ECN offload handling for AccECN series Chia-Yu Chang (Nokia)
  -- strict thread matches above, loose matches on Subject: below --
2026-01-28 14:44 chia-yu.chang

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=20260131164516.4a423230@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=Jason_Livingood@comcast$(echo .)com \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=ast@fiberby$(echo .)net \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=brett.creeley@amd$(echo .)com \
    --cc=cheshire@apple$(echo .)com \
    --cc=chia-yu.chang@nokia-bell-labs$(echo .)com \
    --cc=corbet@lwn$(echo .)net \
    --cc=dave.taht@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=donald.hunter@gmail$(echo .)com \
    --cc=dsahern@kernel$(echo .)org \
    --cc=edumazet@google$(echo .)com \
    --cc=eperezma@redhat$(echo .)com \
    --cc=g.white@cablelabs$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=ij@kernel$(echo .)org \
    --cc=ingemar.s.johansson@ericsson$(echo .)com \
    --cc=jasowang@redhat$(echo .)com \
    --cc=jhs@mojatatu$(echo .)com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=koen.de_schepper@nokia-bell-labs$(echo .)com \
    --cc=kuniyu@google$(echo .)com \
    --cc=leon@kernel$(echo .)org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-kselftest@vger$(echo .)kernel.org \
    --cc=linux-rdma@vger$(echo .)kernel.org \
    --cc=liuhangbin@gmail$(echo .)com \
    --cc=mbloch@nvidia$(echo .)com \
    --cc=mirja.kuehlewind@ericsson$(echo .)com \
    --cc=mst@redhat$(echo .)com \
    --cc=ncardwell@google$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=parav@nvidia$(echo .)com \
    --cc=rs.ietf@gmx$(echo .)at \
    --cc=saeedm@nvidia$(echo .)com \
    --cc=salil.mehta@huawei$(echo .)com \
    --cc=shaojijie@huawei$(echo .)com \
    --cc=shenjian15@huawei$(echo .)com \
    --cc=shuah@kernel$(echo .)org \
    --cc=stephen@networkplumber$(echo .)org \
    --cc=tariqt@nvidia$(echo .)com \
    --cc=vidhi_goel@apple$(echo .)com \
    --cc=virtualization@lists$(echo .)linux.dev \
    --cc=xiyou.wangcong@gmail$(echo .)com \
    --cc=xuanzhuo@linux$(echo .)alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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