From: Ben Hutchings <bhutchings@solarflare.com>
To: "Sebastian Pöhn" <sebastian.belden@googlemail.com>
Cc: "Linux Netdev" <netdev@vger.kernel.org>,
"Sebastian Pöhn" <sebastian.poehn@belden.com>
Subject: Re: [PATCH] ethtool : NFC corrections again
Date: Thu, 14 Jul 2011 02:01:08 +0100 [thread overview]
Message-ID: <1310605268.2756.15.camel@bwh-desktop> (raw)
In-Reply-To: <1309423280.15040.2.camel@DENEC1DT0191>
On Thu, 2011-06-30 at 10:41 +0200, Sebastian Pöhn wrote:
> This patch:
> # Adds an alias for ip4 called l4data pointing to spi (first 4 Layer 4
> bytes)
> # [TRIVIAL] Corrects the permutation of dst and src for ethernet
> # Suggests to always set the ip_ver field of usr_ip to ETH_RX_NFC_IP4 at
> least as long there is no opportunity to use others than IPv4 and there
> is no frontend option to enter ip_ver.
[...]
Applied. Sorry for the delay.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2011-07-14 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 8:41 [PATCH] ethtool : NFC corrections again Sebastian Pöhn
2011-07-14 1:01 ` Ben Hutchings [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=1310605268.2756.15.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.belden@googlemail.com \
--cc=sebastian.poehn@belden.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