From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: netdev@vger.kernel.org, amirv@mellanox.com, ronye@mellanox.com
Subject: Re: [PATCH V1 net 0/2] net/mlx4: fixes for ndo VF control calls
Date: Sat, 11 May 2013 16:13:06 -0700 (PDT) [thread overview]
Message-ID: <20130511.161306.1468839299188078461.davem@davemloft.net> (raw)
In-Reply-To: <1368087755-3606-1-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Thu, 9 May 2013 11:22:33 +0300
> These are two fixes to the mlx4 implementation of ndo_set_vf calls
> we added in the 3.10 merge window.
Series applied, thanks.
prev parent reply other threads:[~2013-05-11 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 8:22 [PATCH V1 net 0/2] net/mlx4: fixes for ndo VF control calls Or Gerlitz
2013-05-09 8:22 ` [PATCH V1 net 1/2] net/mlx4_core: Add missing report on VST and spoof-checking dev caps Or Gerlitz
2013-05-09 8:22 ` [PATCH V1 net 2/2] net/mlx4: Strengthen VLAN tags/priorities enforcement in VST mode Or Gerlitz
2013-05-11 23:13 ` 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=20130511.161306.1468839299188078461.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=ronye@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).