From: Jakub Kicinski <kuba@kernel.org>
To: Joseph Huang <joseph.huang.2024@gmail.com>
Cc: Joseph Huang <Joseph.Huang@garmin.com>,
netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, bridge@lists.linux.dev
Subject: Re: [Patch v3 net-next 0/3] Add support for mdb offload failure notification
Date: Mon, 7 Apr 2025 11:37:58 -0700 [thread overview]
Message-ID: <20250407113758.2fee3e4a@kernel.org> (raw)
In-Reply-To: <af01e665-08bb-4b60-ba0b-1784dd8a5ce3@gmail.com>
On Mon, 7 Apr 2025 14:15:31 -0400 Joseph Huang wrote:
> - Should the re-post be v3 (no change) or v4 (bump)?
Doesn't matter much, but probably v4 is less confusing.
> - Do I re-post after 6.15 is released? Around what time frame (so that I
> can set a reminder)?
No, no, I mean very soon. Like tomorrow. The merge window is when
maintainers merge their tress up, rather than when we merge code
from contributors. It's a bit confusing. Merge window open ==
normal contribution closed, and vice versa.
next prev parent reply other threads:[~2025-04-07 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 21:29 [Patch v3 net-next 0/3] Add support for mdb offload failure notification Joseph Huang
2025-04-04 21:29 ` [Patch v3 net-next 1/3] net: bridge: mcast: Add offload failed mdb flag Joseph Huang
2025-04-05 8:09 ` Nikolay Aleksandrov
2025-04-04 21:29 ` [Patch v3 net-next 2/3] net: bridge: Add offload_fail_notification bopt Joseph Huang
2025-04-04 21:29 ` [Patch v3 net-next 3/3] net: bridge: mcast: Notify on mdb offload failure Joseph Huang
2025-04-05 8:10 ` Nikolay Aleksandrov
2025-04-07 17:29 ` [Patch v3 net-next 0/3] Add support for mdb offload failure notification Jakub Kicinski
2025-04-07 18:15 ` Joseph Huang
2025-04-07 18:37 ` Jakub Kicinski [this message]
2025-04-07 18:40 ` Joseph Huang
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=20250407113758.2fee3e4a@kernel.org \
--to=kuba@kernel.org \
--cc=Joseph.Huang@garmin.com \
--cc=andrew+netdev@lunn.ch \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joseph.huang.2024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.