From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] net: mvneta: introduce tx_csum_limit property
Date: Mon, 15 Jun 2015 16:48:10 +0200 [thread overview]
Message-ID: <20150615164810.0f3c8c8d@free-electrons.com> (raw)
In-Reply-To: <20150615143601.GM7557@n2100.arm.linux.org.uk>
Russell,
On Mon, 15 Jun 2015 15:36:01 +0100, Russell King - ARM Linux wrote:
> On Mon, Jun 15, 2015 at 04:27:22PM +0200, Simon Guinot wrote:
> > This patch introduces the tx_csum_limit DT property. This allows to
> > configure the maximum frame size for which the Ethernet controller is
> > able to perform TCP/IP checksumming. If MTU is set to a value greater
> > than tx_csum_limit, then the features NETIF_F_IP_CSUM and NETIF_F_TSO
> > are disabled.
> >
> > Signed-off-by: Simon Guinot <simon.guinot@sequanux.org>
> > Cc: <stable@vger.kernel.org> # v3.8+
>
> Sorry, I just tripped over this. This looks like a patch adding a new
> _feature_ to this ethernet driver. It isn't a regression fix, and it
> isn't a bug fix. Why are you wanting to get it into stable kernels,
> which are supposed to only have bug and regression fixes applied?
Look at the cover letter, it is fixing a bug.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-15 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 14:27 [PATCH 0/2] Fix Ethernet jumbo frames support for Armada 370 Simon Guinot
2015-06-15 14:27 ` [PATCH 1/2] net: mvneta: introduce tx_csum_limit property Simon Guinot
2015-06-15 14:36 ` Russell King - ARM Linux
2015-06-15 14:48 ` Thomas Petazzoni [this message]
2015-06-15 14:49 ` Thomas Petazzoni
2015-06-15 15:54 ` Simon Guinot
2015-06-16 10:00 ` Thomas Petazzoni
2015-06-16 11:59 ` Jason Cooper
2015-06-15 14:27 ` [PATCH 2/2] ARM: mvebu: disable IP checksum with jumbo frames for Armada 370 Simon Guinot
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=20150615164810.0f3c8c8d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 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).