From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: [dpdk-dev] [PATCH 2/6] i40e: don't refer to eth_dev->pci_dev
Date: Mon, 2 Jan 2017 15:08:46 -0800 [thread overview]
Message-ID: <20170102230850.32610-3-sthemmin@microsoft.com> (raw)
In-Reply-To: <20170102230850.32610-1-sthemmin@microsoft.com>
Later patches remove pci_dev from the ethernet device structure.
Fix the i40e code to just use it's own name when forming zone name.
Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
---
drivers/net/i40e/i40e_fdir.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/i40e/i40e_fdir.c b/drivers/net/i40e/i40e_fdir.c
index 335bf15c..68a2523c 100644
--- a/drivers/net/i40e/i40e_fdir.c
+++ b/drivers/net/i40e/i40e_fdir.c
@@ -250,8 +250,7 @@ i40e_fdir_setup(struct i40e_pf *pf)
}
/* reserve memory for the fdir programming packet */
- snprintf(z_name, sizeof(z_name), "%s_%s_%d",
- eth_dev->driver->pci_drv.driver.name,
+ snprintf(z_name, sizeof(z_name), "i40e_%s_%d",
I40E_FDIR_MZ_NAME,
eth_dev->data->port_id);
mz = i40e_memzone_reserve(z_name, I40E_FDIR_PKT_LEN, SOCKET_ID_ANY);
--
2.11.0
next prev parent reply other threads:[~2017-01-02 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 23:08 [dpdk-dev] [PATCH 0/6] VMBUS and driver infrastructure Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 1/6] ethdev: increase length ethernet device internal name Stephen Hemminger
2017-01-02 23:08 ` Stephen Hemminger [this message]
2017-01-06 1:50 ` [dpdk-dev] [PATCH 2/6] i40e: don't refer to eth_dev->pci_dev Wu, Jingjing
2017-01-02 23:08 ` [dpdk-dev] [PATCH 3/6] vmxnet3: " Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 4/6] cxgbe: " Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 5/6] ethdev: break ethernet driver and pci_driver connection Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 6/6] eal: VMBUS infrastructure Stephen Hemminger
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=20170102230850.32610-3-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=sthemmin@microsoft.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).