From: David Miller <davem@davemloft.net>
To: andrew@lunn.ch
Cc: tharvey@gateworks.com, netdev@vger.kernel.org,
vivien.didelot@savoirfairelinux.com,
linux-kernel@vger.kernel.org, fugang.duan@nxp.com,
imirkin@alum.mit.edu
Subject: Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure
Date: Thu, 31 Aug 2017 10:44:35 -0700 (PDT) [thread overview]
Message-ID: <20170831.104435.1288286218065675397.davem@davemloft.net> (raw)
In-Reply-To: <20170831174141.GP22289@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Thu, 31 Aug 2017 19:41:41 +0200
> Please could you add
>
> fbbeefdd2104 ("net: fec: Allow reception of frames bigger than 1522 bytes")
>
> to stable.
Queued up, thanks.
prev parent reply other threads:[~2017-08-31 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 19:53 DSA mv88e6xxx RX frame errors and TCP/IP RX failure Tim Harvey
2017-08-30 22:06 ` Andrew Lunn
2017-08-31 0:22 ` Tim Harvey
2017-08-31 0:38 ` Ilia Mirkin
2017-08-31 1:46 ` Andrew Lunn
2017-08-31 9:20 ` Maxim Uvarov
2017-08-31 15:37 ` Tim Harvey
2017-08-31 17:41 ` Andrew Lunn
2017-08-31 17:44 ` 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=20170831.104435.1288286218065675397.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=fugang.duan@nxp.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tharvey@gateworks.com \
--cc=vivien.didelot@savoirfairelinux.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).