From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: netdev@vger.kernel.org, amirv@mellanox.com
Subject: Re: [PATCH net-next 0/6] net/mlx4: Add support to SRIOV VF management ndo calls
Date: Wed, 24 Apr 2013 16:30:49 -0400 (EDT) [thread overview]
Message-ID: <20130424.163049.2212021825718596200.davem@davemloft.net> (raw)
In-Reply-To: <1366821674-17902-1-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Wed, 24 Apr 2013 19:41:08 +0300
> This series adds support for the SRIOV ndo_set_vf callbacks to the mlx4 driver.
>
> Series done against the net-next tree as of commit 0c501345c "batman-adv: fix
> global protection fault during soft_iface destruction".
>
> We have successfully tested the series on net-next, except for getting
> the VF link info issue I have reported earlier today on netdev, we
> see the problem for both ixgbe and mlx4 VFs. Just to make sure get
> VF config is working OK with patch #6 - we have run it over 3.8.8 too.
Series applied, thanks.
next prev parent reply other threads:[~2013-04-24 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 16:41 [PATCH net-next 0/6] net/mlx4: Add support to SRIOV VF management ndo calls Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 1/6] net/mlx4: Add reference counting to MAC registeration Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 2/6] net/mlx4: Add structures to keep VF Ethernet ports information Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 3/6] net/mlx4: Add set VF mac address support Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 4/6] net/mlx4: Add set VF default vlan ID and priority support Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 5/6] net/mlx4: Add VF MAC spoof checking support Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 6/6] net/mlx4: Add support to get VF config Or Gerlitz
2013-04-24 20:30 ` David Miller [this message]
2013-04-25 8:11 ` [PATCH net-next 0/6] net/mlx4: Add support to SRIOV VF management ndo calls Or Gerlitz
2013-04-25 8:33 ` David Miller
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=20130424.163049.2212021825718596200.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@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).