public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: "Théo Lebrun" <theo.lebrun@bootlin•com>
Cc: "Nicolai Buchwitz" <nb@tipi-net•de>,
	<nicolas.ferre@microchip•com>, <claudiu.beznea@tuxon•dev>,
	<andrew+netdev@lunn•ch>, <davem@davemloft•net>,
	<edumazet@google•com>, <pabeni@redhat•com>,
	<netdev@vger•kernel.org>
Subject: Re: [PATCH net-next] net: macb: allow MTU changes while the interface is running
Date: Wed, 18 Mar 2026 15:13:39 -0700	[thread overview]
Message-ID: <20260318151339.398e57f0@kernel.org> (raw)
In-Reply-To: <DH5TETVK34CG.V7P9P9Z1AAKL@bootlin.com>

On Wed, 18 Mar 2026 10:53:37 +0100 Théo Lebrun wrote:
> Goal is to keep `bp->queues` & co as before, to minimise the diff.

Minimizing the diff isn't really a goal usually.
As long as you separate out large mechanical changes so that it's easy
to scan thru them and confirm they are correct it's not a problem.
Of course if there's a mix of functional changes and renames that's 
a nightmare.

  parent reply	other threads:[~2026-03-18 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  9:27 [PATCH net-next] net: macb: allow MTU changes while the interface is running Nicolai Buchwitz
2026-03-17 17:00 ` Théo Lebrun
2026-03-17 19:31   ` Nicolai Buchwitz
2026-03-17 22:23   ` Jakub Kicinski
2026-03-17 22:58     ` Nicolai Buchwitz
2026-03-17 23:23       ` Jakub Kicinski
2026-03-18  9:53         ` Théo Lebrun
2026-03-18 11:25           ` Nicolai Buchwitz
2026-03-18 14:33             ` Théo Lebrun
2026-03-18 22:13           ` Jakub Kicinski [this message]
2026-03-17 19:42 ` Breno Leitao
2026-03-17 19:47   ` Breno Leitao
2026-03-17 20:11     ` Nicolai Buchwitz
2026-03-17 20:04   ` Nicolai Buchwitz

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=20260318151339.398e57f0@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=claudiu.beznea@tuxon$(echo .)dev \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=nb@tipi-net$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=nicolas.ferre@microchip$(echo .)com \
    --cc=pabeni@redhat$(echo .)com \
    --cc=theo.lebrun@bootlin$(echo .)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