From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/3] Remove inet_lro remnants
Date: Mon, 19 Nov 2012 19:14:42 -0500 (EST) [thread overview]
Message-ID: <20121119.191442.1430422530127159786.davem@davemloft.net> (raw)
In-Reply-To: <1353105635.2743.49.camel@bwh-desktop.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 16 Nov 2012 22:40:35 +0000
> Eric's comments on LRO/GRO conversion prompted me to check what was
> still using inet_lro. Not very many drivers, but there are a few
> unnecessary references outside the code.
Series applied, thanks Ben.
prev parent reply other threads:[~2012-11-20 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 22:40 [PATCH net-next 0/3] Remove inet_lro remnants Ben Hutchings
2012-11-16 22:44 ` [PATCH net-next 1/3] mlx4_en: Remove remnants of LRO support Ben Hutchings
2012-11-18 9:03 ` Amir Vadai
2012-11-18 9:09 ` Amir Vadai
2012-11-16 22:46 ` [PATCH net-next 2/3] ehea: " Ben Hutchings
2012-11-16 22:47 ` [PATCH net-next 3/3] net: Remove bogus dependencies on INET Ben Hutchings
2012-11-20 0:14 ` 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=20121119.191442.1430422530127159786.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=eric.dumazet@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 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).