netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: netdev@vger.kernel.org, Yehezkel Bernat <YehezkelShB@gmail.com>,
	Ian MacDonald <ian@netstatz.com>,
	Salvatore Bonaccorso <carnil@debian.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jay Vosburgh <jv@jvosburgh.net>
Subject: Re: [PATCH net-next v2 0/5] net: thunderbolt: Various improvements
Date: Mon, 15 Dec 2025 14:46:09 +0000	[thread overview]
Message-ID: <aUAfMYxit0aC_BZa@horms.kernel.org> (raw)
In-Reply-To: <20251215121109.4042218-1-mika.westerberg@linux.intel.com>

On Mon, Dec 15, 2025 at 01:11:04PM +0100, Mika Westerberg wrote:
> Hi all,
> 
> This series improves the Thunderbolt networking driver so that it should
> work with the bonding driver. I added also possibility of channing MTU
> which is sometimes needed, and was part of the original driver.
> 
> The discussion that started this patch series can be read below:
> 
>   https://lore.kernel.org/netdev/CAFJzfF9N4Hak23sc-zh0jMobbkjK7rg4odhic1DQ1cC+=MoQoA@mail.gmail.com/
> 
> The previous version of the series can be seen here:
> 
>   v1: https://lore.kernel.org/netdev/20251127131521.2580237-1-mika.westerberg@linux.intel.com/

...

## Form letter - net-next-closed

net-next is currently closed for new drivers, features, code refactoring and
optimizations. We are currently accepting bug fixes only.

net-next was closed when the merge window for v6.19 began. And due to a
combination of the travel commitments of the maintainers, and the holiday
season, net-next will not re-open until after 2nd January.

Please repost when net-next reopens.

RFC patches sent for review only are welcome at any time.

Thanks for your understanding.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle

-- 
pw-bot: defer

      parent reply	other threads:[~2025-12-15 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 12:11 [PATCH net-next v2 0/5] net: thunderbolt: Various improvements Mika Westerberg
2025-12-15 12:11 ` [PATCH net-next v2 1/5] net: thunderbolt: Allow changing MAC address of the device Mika Westerberg
2025-12-15 12:11 ` [PATCH net-next v2 2/5] net: thunderbolt: Allow changing MTU " Mika Westerberg
2025-12-15 12:11 ` [PATCH net-next v2 3/5] net: ethtool: Add define for SPEED_80000 Mika Westerberg
2025-12-15 12:11 ` [PATCH net-next v2 4/5] bonding: 3ad: Add support " Mika Westerberg
2025-12-15 12:11 ` [PATCH net-next v2 5/5] net: thunderbolt: Allow reading link settings Mika Westerberg
2025-12-15 14:46 ` Simon Horman [this message]

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=aUAfMYxit0aC_BZa@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=YehezkelShB@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=carnil@debian.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ian@netstatz.com \
    --cc=jv@jvosburgh.net \
    --cc=kuba@kernel.org \
    --cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).