From: David Miller <davem@davemloft.net>
To: yanb@mellanox.com
Cc: ogerlitz@mellanox.com, amirv@mellanox.com,
netdev@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: [PATCH net-next] net: ethool: Document struct ethtool_flow_ext
Date: Thu, 13 Dec 2012 13:01:57 -0500 (EST) [thread overview]
Message-ID: <20121213.130157.1673103392332847815.davem@davemloft.net> (raw)
In-Reply-To: <1355412059-25663-1-git-send-email-yanb@mellanox.com>
From: Yan Burman <yanb@mellanox.com>
Date: Thu, 13 Dec 2012 17:20:59 +0200
> Add documentation for struct ethtool_flow_ext especially in regard
> to what flags are needed for which fields.
>
> Signed-off-by: Yan Burman <yanb@mellanox.com>
Applied.
prev parent reply other threads:[~2012-12-13 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 15:20 [PATCH net-next] net: ethool: Document struct ethtool_flow_ext Yan Burman
2012-12-13 16:27 ` Ben Hutchings
2012-12-13 18:01 ` 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=20121213.130157.1673103392332847815.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yanb@mellanox.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).