From: Jeff Garzik <jeff@garzik.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH ethtool 1/2] ethtool: Use inet_aton() to parse IPv4 addresses for RX n-tuple control
Date: Wed, 04 Aug 2010 16:36:53 -0400 [thread overview]
Message-ID: <4C59CF65.2060801@garzik.org> (raw)
In-Reply-To: <1279825899.2104.28.camel@achroite.uk.solarflarecom.com>
FYI, I'm about to roll a new ethtool release for kernel 2.6.35. Are
these two patches the only outstanding ones? (they look good, will be
applied)
Jeff
P.S. The maintainer address is jgarzik@pobox.com, my standard kernel
address. jgarzik@redhat.com has a much higher latency, as it doesn't
get used very much.
next prev parent reply other threads:[~2010-08-04 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 19:11 [PATCH ethtool 1/2] ethtool: Use inet_aton() to parse IPv4 addresses for RX n-tuple control Ben Hutchings
2010-07-22 19:12 ` [PATCH ethtool 2/2] ethtool: Remove specification of number bases for RX-ntuple parameters Ben Hutchings
2010-08-04 20:36 ` Jeff Garzik [this message]
2010-08-04 20:51 ` [PATCH ethtool 1/2] ethtool: Use inet_aton() to parse IPv4 addresses for RX n-tuple control Ben Hutchings
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=4C59CF65.2060801@garzik.org \
--to=jeff@garzik.org \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.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.