From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3 v2] ixgbe fixes
Date: Mon, 29 Feb 2016 17:03:31 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836B0C491@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <1456498163-26619-1-git-send-email-bernard.iremonger@intel.com>
> -----Original Message-----
> From: Iremonger, Bernard
> Sent: Friday, February 26, 2016 2:49 PM
> To: dev@dpdk.org
> Cc: Ananyev, Konstantin; Zhang, Helin; Iremonger, Bernard
> Subject: [PATCH 0/3 v2] ixgbe fixes
>
> This patch set implements the following:
> Removes code which was duplicated in eth_ixgbevf_dev_init().
> Adds more information to the error message in ixgbe_check_mq_mode().
> Allows the MAC address of the VF to be set to zero.
>
> Changes in v2:
> Do not overwrite the VF perm_add with zero.
>
> Bernard Iremonger (3):
> ixgbe: cleanup eth_ixgbevf_dev_uninit
> ixgbe: add more information to the error message
> ixgbe: fix setting of VF MAC address
>
> drivers/net/ixgbe/ixgbe_ethdev.c | 29 +++++++++++++----------------
> drivers/net/ixgbe/ixgbe_pf.c | 7 ++++---
> 2 files changed, 17 insertions(+), 19 deletions(-)
>
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.6.3
next prev parent reply other threads:[~2016-02-29 17:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:19 [dpdk-dev] [PATCH 0/3] " Bernard Iremonger
2016-02-24 16:19 ` [dpdk-dev] [PATCH 1/3] ixgbe: cleanup eth_ixgbevf_dev_uninit Bernard Iremonger
2016-02-24 16:19 ` [dpdk-dev] [PATCH 2/3] ixgbe: add more information to the error message Bernard Iremonger
2016-02-24 16:19 ` [dpdk-dev] [PATCH 3/3] ixgbe: allow use of zero MAC address with VF Bernard Iremonger
2016-02-26 14:49 ` [dpdk-dev] [PATCH 0/3 v2] ixgbe fixes Bernard Iremonger
2016-02-26 14:49 ` [dpdk-dev] [PATCH 1/3 v2] ixgbe: cleanup eth_ixgbevf_dev_uninit Bernard Iremonger
2016-02-26 14:49 ` [dpdk-dev] [PATCH 2/3 v2] ixgbe: add more information to the error message Bernard Iremonger
2016-02-26 14:49 ` [dpdk-dev] [PATCH 3/3 v2] ixgbe: fix setting of VF MAC address Bernard Iremonger
2016-02-29 17:03 ` Ananyev, Konstantin [this message]
2016-03-07 17:38 ` [dpdk-dev] [PATCH v3 0/3] ixgbe fixes Bernard Iremonger
2016-03-07 17:38 ` [dpdk-dev] [PATCH v3 1/3] ixgbe: cleanup eth_ixgbevf_dev_uninit Bernard Iremonger
2016-03-07 17:38 ` [dpdk-dev] [PATCH v3 2/3] ixgbe: add more information to the error message Bernard Iremonger
2016-03-07 17:38 ` [dpdk-dev] [PATCH v3 3/3] ixgbe: fix dev_close to remove VF MAC address Bernard Iremonger
2016-03-08 17:10 ` [dpdk-dev] [PATCH v4 0/3] ixgbe fixes Bernard Iremonger
2016-03-08 17:10 ` [dpdk-dev] [PATCH v4 1/3] ixgbe: cleanup eth_ixgbevf_dev_uninit Bernard Iremonger
2016-03-08 17:10 ` [dpdk-dev] [PATCH v4 2/3] ixgbe: add more information to the error message Bernard Iremonger
2016-03-08 17:10 ` [dpdk-dev] [PATCH v4 3/3] ixgbe: fix dev_close to remove VF MAC address Bernard Iremonger
2016-03-09 13:17 ` Ananyev, Konstantin
2016-03-11 17:19 ` [dpdk-dev] [PATCH v4 0/3] ixgbe fixes Bruce Richardson
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=2601191342CEEE43887BDE71AB97725836B0C491@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
/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).