All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nelson.chang@mediatek.com
Cc: john@phrozen.org, f.fainelli@gmail.com, nbd@openwrt.org,
	netdev@vger.kernel.org, linux-mediatek@lists.infradead.org,
	nelsonch.tw@gmail.com
Subject: Re: [PATCH net-next v2 0/3] net: ethernet: mediatek: add HW LRO functions
Date: Sat, 17 Sep 2016 09:46:26 -0400 (EDT)	[thread overview]
Message-ID: <20160917.094626.1566729007953672684.davem@davemloft.net> (raw)
In-Reply-To: <1473832739-4983-1-git-send-email-nelson.chang@mediatek.com>

From: Nelson Chang <nelson.chang@mediatek.com>
Date: Wed, 14 Sep 2016 13:58:56 +0800

> The series add the large receive offload (LRO) functions by hardware and
> the ethtool functions to configure RX flows of HW LRO.
> 
> changes since v2:
> - Add ndo_fix_features to prevent NETIF_F_LRO off while RX flow is programmed
> - Rephrase the dts property is a capability if the hardware supports LRO
> 
> changes since v1:
> - Add HW LRO support
> - Add ethtool hooks to set LRO RX flows

This doesn't apply cleanly to net-next.

  parent reply	other threads:[~2016-09-17 13:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  5:58 [PATCH net-next v2 0/3] net: ethernet: mediatek: add HW LRO functions Nelson Chang
2016-09-14  5:58 ` Nelson Chang
2016-09-14  5:58 ` [PATCH net-next v2 1/3] net: ethernet: mediatek: add HW LRO functions of PDMA RX rings Nelson Chang
2016-09-14  5:58   ` Nelson Chang
2016-09-14  5:58 ` [PATCH net-next v2 2/3] net: ethernet: mediatek: add ethtool functions to configure RX flows of HW LRO Nelson Chang
2016-09-14  5:58   ` Nelson Chang
2016-09-14  5:58 ` [PATCH net-next v2 3/3] net: ethernet: mediatek: add the dts property to set if the HW supports LRO Nelson Chang
2016-09-14  5:58   ` Nelson Chang
2016-09-17 13:46 ` David Miller [this message]
2016-09-17 15:50 [PATCH net-next v2 0/3] net: ethernet: mediatek: add HW LRO functions Nelson Chang
2016-09-17 15:50 ` Nelson Chang
2016-09-17 15:50 Nelson Chang
2016-09-17 15:50 ` Nelson Chang

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=20160917.094626.1566729007953672684.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=john@phrozen.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=nbd@openwrt.org \
    --cc=nelson.chang@mediatek.com \
    --cc=nelsonch.tw@gmail.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.