From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/2] clean up interrupt handle
Date: Tue, 04 Apr 2017 12:12:33 +0200 [thread overview]
Message-ID: <6430789.TYnjRxi5iG@xps13> (raw)
In-Reply-To: <20170331020913.19004-1-qi.z.zhang@intel.com>
Hi,
2017-03-30 22:09, Qi Zhang:
> It seems its not necessary to register an intr_handle for interrupt callback
> function. "void* cb_arg" shows enough when be used to pass the object that
> contain the information be required to handle the interrupt event( A typical
> way which is implemented by almost all driver is by passing a rte_ethdev
> instance). The patch change the prototype of rte_intr_callback_fn by removing
> the uncessary intr_handle paramter.
>
> v3:
> - update bnx2x driver which is missed in v1,v2
>
> v2:
> - seperate patch 1 in v1 into 2 patches.
> - correct some commit log.
>
> Qi Zhang (2):
> eal: clean up interrupt handle
> app/test: update test code
Several comments:
* You forgot to use --in-reply-to, so it is not convenient to check the history.
* Please keep the the prior acked-by in your patches if there are.
* There is another miss in this patch:
drivers/net/mlx5/mlx5_ethdev.c:1259:10:
fatal error: incompatible pointer types passing
'void (struct rte_intr_handle *, void *)'
to parameter of type 'rte_intr_callback_fn'
(aka 'void (*)(void *)') [-Wincompatible-pointer-types]
mlx5_dev_interrupt_handler,
* The second patch is clearly not up to date as the file
app/test/test_interrupts.c has moved.
next prev parent reply other threads:[~2017-04-04 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 2:09 Qi Zhang
2017-03-31 2:09 ` [dpdk-dev] [PATCH v3 1/2] eal: " Qi Zhang
2017-03-31 2:09 ` [dpdk-dev] [PATCH v3 2/2] app/test: update test code Qi Zhang
2017-04-04 10:12 ` Thomas Monjalon [this message]
2017-04-04 12:41 ` [dpdk-dev] [PATCH v3 0/2] clean up interrupt handle Zhang, Qi Z
2017-04-04 21:21 ` [dpdk-dev] [PATCH v4 " Qi Zhang
2017-04-04 21:21 ` [dpdk-dev] [PATCH v4 1/2] vfio: keep interrupt source read only Qi Zhang
2017-04-04 21:21 ` [dpdk-dev] [PATCH v4 2/2] eal: clean up interrupt handle Qi Zhang
2017-04-04 13:54 ` Shahaf Shuler
2017-04-04 14:23 ` Zhang, Qi Z
2017-04-04 22:27 ` [dpdk-dev] [PATCH v5 0/2] " Qi Zhang
2017-04-04 14:50 ` Thomas Monjalon
2017-04-04 14:58 ` Zhang, Qi Z
2017-04-04 22:27 ` [dpdk-dev] [PATCH v5 1/2] vfio: keep interrupt source read only Qi Zhang
2017-04-04 22:27 ` [dpdk-dev] [PATCH v5 2/2] eal: clean up interrupt handle Qi Zhang
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=6430789.TYnjRxi5iG@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.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).