All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
	"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: min/max mtu field in struct net_device
Date: Mon, 14 Nov 2016 10:30:59 +0100	[thread overview]
Message-ID: <1479115859.7899.3.camel@sipsolutions.net> (raw)
In-Reply-To: <c4682854-87ce-5e28-d049-545f24d48cab@broadcom.com> (sfid-20161114_095807_156709_13DD77F5)

On Mon, 2016-11-14 at 09:49 +0100, Arend Van Spriel wrote:
> Just wondering. Does anyone have any ideas on how to backport the two
> patches below. The struct net_device now holds mtu range which
> network subsystem checks. For a number of drivers and mac80211 it
> means they no longer have .ndo_change_mtu callback. My guess is that
> we need patches in backport of some sort to tackle this.

Yeah, I kinda saw this coming. Since in almost all cases using the new
min/max the ndo_change_mtu was actually removed, perhaps we can come up
with a way to spatch it back in?

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2016-11-14  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  8:49 min/max mtu field in struct net_device Arend Van Spriel
2016-11-14  9:30 ` Johannes Berg [this message]
2016-11-14 10:46   ` Arend Van Spriel
2016-11-14 13:27     ` Johannes Berg
2016-11-15  8:36     ` Fwd: " Arend Van Spriel
2016-11-17 20:36       ` [Cocci] Fwd: " Arend Van Spriel
2016-11-17 22:48         ` Julia Lawall
2016-11-18  9:01           ` Arend van Spriel
2016-11-18 11:10             ` Julia Lawall
2016-11-19 11:12             ` Arend van Spriel
2016-11-19 12:52               ` Julia Lawall

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=1479115859.7899.3.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=backports@vger.kernel.org \
    /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.