From: Stephen Hemminger <stephen@networkplumber.org>
To: Rasesh Mody <rasesh.mody@qlogic.com>
Cc: <thomas.monjalon@6wind.com>, <bruce.richardson@intel.com>,
<dev@dpdk.org>, <ameen.rahman@qlogic.com>,
<harish.patil@qlogic.com>, <sony.chacko@qlogic.com>
Subject: Re: [dpdk-dev] [PATCH v3 05/10] qede: Add core driver
Date: Mon, 21 Mar 2016 10:32:44 -0700 [thread overview]
Message-ID: <20160321103244.4e158f5d@xeon-e3> (raw)
In-Reply-To: <1458348805-32648-6-git-send-email-rasesh.mody@qlogic.com>
On Fri, 18 Mar 2016 17:53:20 -0700
Rasesh Mody <rasesh.mody@qlogic.com> wrote:
> +static struct eth_dev_ops qede_eth_dev_ops = {
> + .dev_configure = qede_dev_configure,
> + .dev_infos_get = qede_dev_info_get,
> + .rx_queue_setup = qede_rx_queue_setup,
> + .rx_queue_release = qede_rx_queue_release,
> + .tx_queue_setup = qede_tx_queue_setup,
> + .tx_queue_release = qede_tx_queue_release,
> + .dev_start = qede_dev_start,
> + .dev_set_link_up = qede_dev_set_link_up,
> + .dev_set_link_down = qede_dev_set_link_down,
> + .link_update = qede_link_update,
> + .promiscuous_enable = qede_promiscuous_enable,
> + .promiscuous_disable = qede_promiscuous_disable,
> + .allmulticast_enable = qede_allmulticast_enable,
> + .allmulticast_disable = qede_allmulticast_disable,
> + .dev_stop = qede_dev_stop,
> + .dev_close = qede_dev_close,
> + .stats_get = qede_get_stats,
> + .mac_addr_add = qede_mac_addr_add,
> + .mac_addr_remove = qede_mac_addr_remove,
> + .vlan_offload_set = qede_vlan_offload_set,
> + .vlan_filter_set = qede_vlan_filter_set,
> + .flow_ctrl_set = qede_flow_ctrl_set,
> + .flow_ctrl_get = qede_flow_ctrl_get,
> +};
> +
All eth_dev_ops structures should be marked const.
It makes it harder for attacker to find a handle.
next prev parent reply other threads:[~2016-03-21 17:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 0:53 [dpdk-dev] [PATCH v3 00/10] qede: Add qede PMD Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 01/10] qede: Add maintainers Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 02/10] qede: Add documentation Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 03/10] qede: Add license file Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 04/10] qede: Add base driver Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 05/10] qede: Add core driver Rasesh Mody
2016-03-21 17:32 ` Stephen Hemminger [this message]
2016-03-22 1:14 ` Rasesh Mody
2016-03-22 10:55 ` Bruce Richardson
2016-03-22 11:03 ` Bruce Richardson
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 06/10] qede: Add L2 support Rasesh Mody
2016-03-22 11:04 ` Bruce Richardson
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 07/10] qede: Add SRIOV support Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 08/10] qede: Add attention support Rasesh Mody
2016-03-22 11:07 ` Bruce Richardson
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 09/10] qede: Add DCBX support Rasesh Mody
2016-03-19 0:53 ` [dpdk-dev] [PATCH v3 10/10] qede: Enable PMD build Rasesh Mody
2016-03-22 11:21 ` Bruce Richardson
2016-03-22 11:21 ` [dpdk-dev] [PATCH v3 00/10] qede: Add qede PMD Richardson, Bruce
2016-03-22 11:30 ` Bruce Richardson
2016-03-29 20:52 ` Rasesh Mody
2016-03-30 12:34 ` Bruce Richardson
2016-03-24 1:52 ` Rasesh Mody
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=20160321103244.4e158f5d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ameen.rahman@qlogic.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.com \
--cc=rasesh.mody@qlogic.com \
--cc=sony.chacko@qlogic.com \
--cc=thomas.monjalon@6wind.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).