From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: santwona.behera@sun.com, peter.p.waskiewicz.jr@intel.com,
netdev@vger.kernel.org, linux-net-drivers@solarflare.com,
dm@chelsio.com
Subject: Re: [PATCH net-next-2.6] ethtool: Complete kernel-doc comments for RX flow filter and hash control
Date: Wed, 08 Sep 2010 14:05:12 -0700 (PDT) [thread overview]
Message-ID: <20100908.140512.242117688.davem@davemloft.net> (raw)
In-Reply-To: <1283870780.2270.12.camel@achroite.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Tue, 07 Sep 2010 15:46:20 +0100
> On Tue, 2010-09-07 at 15:41 +0100, Ben Hutchings wrote:
>> There are now several interfaces within the ethtool API for getting
>> and setting RX flow filtering and hashing behaviour, most of which are
>> poorly documented. This adds kernel-doc comments for all these
>> interfaces, based on the existing incomplete comments and on the
>> initial implementations.
>>
>> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
>> ---
>> Santwona, Peter,
>>
>> Please point out any errors and any information that should be added to
>> the comments to explain the significant differences between the RXNFC
>> and RXNTUPLE interfaces.
> [...]
>> +/**
>> + * struct ethtool_rx_ntuple - command to get or set RX flow filter
>> + * @cmd: Specific command number - %ETHTOOL_GRXNTUPLE or %ETHTOOL_SRXNTUPLE
>
> Of course this is wrong - ETHTOOL_GRXNTUPLE uses struct ethtool_gstrings
> instead.
Ben, please submit a fixed up version of the patch.
Thanks.
next prev parent reply other threads:[~2010-09-08 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 14:41 [PATCH net-next-2.6] ethtool: Complete kernel-doc comments for RX flow filter and hash control Ben Hutchings
2010-09-07 14:46 ` Ben Hutchings
2010-09-08 21:05 ` David Miller [this message]
2010-09-09 13:52 ` Ben Hutchings
2010-09-10 0:50 ` Peter P Waskiewicz Jr
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=20100908.140512.242117688.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=dm@chelsio.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=santwona.behera@sun.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).