From: Stephen Hemminger <stephen@networkplumber.org>
To: Jan Medala <jan@semihalf.com>
Cc: dev@dpdk.org, matua@amazon.com,
Evgeny Schemeilin <evgenys@amazon.com>,
Jakub Palider <jpa@semihalf.com>
Subject: Re: [dpdk-dev] [PATCH v8 4/4] ena: DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA)
Date: Mon, 21 Mar 2016 10:33:32 -0700 [thread overview]
Message-ID: <20160321103332.02db0008@xeon-e3> (raw)
In-Reply-To: <1458225078-17105-5-git-send-email-jan@semihalf.com>
On Thu, 17 Mar 2016 15:31:18 +0100
Jan Medala <jan@semihalf.com> wrote:
> +static struct eth_dev_ops ena_dev_ops = {
> + .dev_configure = ena_dev_configure,
> + .dev_infos_get = ena_infos_get,
> + .rx_queue_setup = ena_rx_queue_setup,
> + .tx_queue_setup = ena_tx_queue_setup,
> + .dev_start = ena_start,
> + .link_update = ena_link_update,
> + .stats_get = ena_stats_get,
> + .mtu_set = ena_mtu_set,
> + .rx_queue_release = ena_rx_queue_release,
> + .tx_queue_release = ena_tx_queue_release,
> + .dev_close = ena_close,
> + .reta_update = ena_rss_reta_update,
> + .reta_query = ena_rss_reta_query,
> +};
> +
Why is ena_dev_ops not const?
next prev parent reply other threads:[~2016-03-21 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 14:31 [dpdk-dev] [PATCH v8 0/4] " Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 1/4] ena: Amazon ENA documentation Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 2/4] ena: Amazon ENA communication layer Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 3/4] ena: Amazon ENA communication layer for DPDK platform Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 4/4] ena: DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA) Jan Medala
2016-03-18 17:17 ` Bruce Richardson
2016-03-21 17:33 ` Stephen Hemminger [this message]
2016-03-18 17:04 ` [dpdk-dev] [PATCH v8 0/4] " Bruce Richardson
2016-03-18 17:11 ` Jan Mędala
2016-03-18 17:19 ` 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=20160321103332.02db0008@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=jan@semihalf.com \
--cc=jpa@semihalf.com \
--cc=matua@amazon.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).