From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: jarod@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
qca_merez@qca.qualcomm.com, simon@thekelleys.org.uk,
stas.yakovlev@gmail.com, inaky.perez-gonzalez@intel.com
Subject: Re: [PATCH net-next v2 3/9] net: use core MTU range checking in wireless drivers
Date: Thu, 20 Oct 2016 14:38:00 -0400 (EDT) [thread overview]
Message-ID: <20161020.143800.2192559431314444033.davem@davemloft.net> (raw)
In-Reply-To: <1476987755.14078.3.camel@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu, 20 Oct 2016 20:22:35 +0200
> On Thu, 2016-10-20 at 13:55 -0400, Jarod Wilson wrote:
>> - set max_mtu in wil6210 driver
>> - set max_mtu in atmel driver
>> - set min/max_mtu in cisco airo driver, remove airo_change_mtu
>> - set min/max_mtu in ipw2100/ipw2200 drivers, remove
>> libipw_change_mtu
>> - set min/max_mtu in p80211netdev, remove wlan_change_mtu
>> - set min/max_mtu in net/mac80211/iface.c and remove ieee80211_change_mtu
>
> For the mac80211 part,
>
> Acked-by: Johannes Berg <johannes@sipsolutions.net>
>
> Dave, I'm assuming you'll pick this up, but if you prefer not to I can
> also coordinate with Kalle to take this through our trees.
Yeah I'll get this, thanks for asking.
prev parent reply other threads:[~2016-10-20 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161019023333.15760-1-jarod@redhat.com>
2016-10-19 2:33 ` [PATCH net-next 2/6] net: use core MTU range checking in wireless drivers Jarod Wilson
2016-10-19 7:38 ` Johannes Berg
2016-10-19 14:27 ` Jarod Wilson
2016-10-19 14:28 ` Johannes Berg
[not found] ` <20161020175524.6184-1-jarod@redhat.com>
2016-10-20 17:55 ` [PATCH net-next v2 3/9] " Jarod Wilson
2016-10-20 18:22 ` Johannes Berg
2016-10-20 18:38 ` David Miller [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=20161020.143800.2192559431314444033.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=inaky.perez-gonzalez@intel.com \
--cc=jarod@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qca_merez@qca.qualcomm.com \
--cc=simon@thekelleys.org.uk \
--cc=stas.yakovlev@gmail.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).