From: David Miller <davem@davemloft.net>
To: yevgenyp@mellanox.co.il
Cc: netdev@vger.kernel.org, eugenia@mellanox.co.il
Subject: Re: [PATCH net V1 0/6] mlx4: Fixes and enhancements to SRIOV code.
Date: Sun, 22 Jan 2012 14:23:31 -0500 (EST) [thread overview]
Message-ID: <20120122.142331.1772998493613978921.davem@davemloft.net> (raw)
In-Reply-To: <4F18721E.5040901@mellanox.co.il>
From: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Date: Thu, 19 Jan 2012 21:42:22 +0200
> Hello Dave,
>
> This is V1 of a series of enhancements and some fixes for mlx4 SRIOV code.
> Main changes are:
> - Correct ethtool statistics report for each VF/PF.
> - The ability of each function to decide on which event queue to receive asynchronous events.
> - Bug fixes.
All applied, thanks.
prev parent reply other threads:[~2012-01-22 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 19:42 [PATCH net V1 0/6] mlx4: Fixes and enhancements to SRIOV code Yevgeny Petrilin
2012-01-22 19:23 ` 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=20120122.142331.1772998493613978921.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eugenia@mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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).