From: David Miller <davem@davemloft.net>
To: tlfalcon@linux.vnet.ibm.com
Cc: brking@linux.vnet.ibm.com, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/5] ibmveth: change rx buffer default allocation for CMO
Date: Tue, 14 Apr 2015 16:53:58 -0400 (EDT) [thread overview]
Message-ID: <20150414.165358.1395447624110804420.davem@davemloft.net> (raw)
In-Reply-To: <1429043704-22552-1-git-send-email-tlfalcon@linux.vnet.ibm.com>
The net-next tree is closed, so new feature submissions are not appropriate at this
time.
prev parent reply other threads:[~2015-04-14 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 20:35 [PATCH 1/5] ibmveth: change rx buffer default allocation for CMO Thomas Falcon
2015-04-14 20:35 ` [PATCH 2/5] ibmveth: Add support for TSO Thomas Falcon
2015-04-14 20:35 ` [PATCH 3/5] ibmveth: Add GRO support Thomas Falcon
2015-04-14 20:35 ` [PATCH 4/5] ibmveth: Add support for Large Receive Offload Thomas Falcon
2015-04-14 22:00 ` Eric Dumazet
2015-04-21 18:59 ` Thomas Falcon
2015-04-14 20:35 ` [PATCH 5/5] ibmveth: Add ethtool statistics for tx and rx large packets Thomas Falcon
2015-04-14 20:53 ` 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=20150414.165358.1395447624110804420.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brking@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=tlfalcon@linux.vnet.ibm.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).