From: David Miller <davem@davemloft.net>
To: fillods@users.sf.net
Cc: netdev@vger.kernel.org, steve.glendinning@smsc.com
Subject: Re: [PATCH] net: usb: smsc75xx: fix mtu
Date: Mon, 16 Apr 2012 23:54:43 -0400 (EDT) [thread overview]
Message-ID: <20120416.235443.1617997001955260332.davem@davemloft.net> (raw)
In-Reply-To: <20120415213829.GI5277@charybde.local>
From: Stephane Fillod <fillods@users.sf.net>
Date: Sun, 15 Apr 2012 23:38:29 +0200
> Make smsc75xx recalculate the hard_mtu after adjusting the
> hard_header_len.
>
> Without this, usbnet adjusts the MTU down to 1492 bytes, and the host is
> unable to receive standard 1500-byte frames from the device.
>
> Inspired by same fix on cdc_eem 78fb72f7936c01d5b426c03a691eca082b03f2b9.
>
> Tested on ARM/Omap3 with EVB-LAN7500-LC.
>
> Signed-off-by: Stephane Fillod <fillods@users.sf.net>
Applied, thanks.
prev parent reply other threads:[~2012-04-17 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 21:38 [PATCH] net: usb: smsc75xx: fix mtu Stephane Fillod
2012-04-17 3:54 ` 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=20120416.235443.1617997001955260332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fillods@users.sf.net \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@smsc.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).