From: David Miller <davem@davemloft.net>
To: u.kleine-koenig@pengutronix.de
Cc: netdev@vger.kernel.org, andrew@lunn.ch, kernel@pengutronix.de
Subject: Re: add "net: fec: Allow reception of frames bigger than 1522 bytes" to stable
Date: Wed, 06 Dec 2017 16:29:35 -0500 (EST) [thread overview]
Message-ID: <20171206.162935.2259258305397185128.davem@davemloft.net> (raw)
In-Reply-To: <20171206212450.nhimhjwusmmxe7na@pengutronix.de>
From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date: Wed, 6 Dec 2017 22:24:50 +0100
> Hello,
>
> on an 4.9.x kernel using the freescale/fec driver "behind" a switch I
> had problems with packet reception.
>
> Commit fbbeefdd2104 ("net: fec: Allow reception of frames bigger than
> 1522 bytes") fixed it for me and so I suggest to queue that one for
> stable. It can be cherry-picked to 4.9.x without conflict and IMHO
> should be applied to all stable branches before v4.14.
Ok, queued up.
prev parent reply other threads:[~2017-12-06 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 21:24 add "net: fec: Allow reception of frames bigger than 1522 bytes" to stable Uwe Kleine-König
2017-12-06 21:29 ` 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=20171206.162935.2259258305397185128.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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