DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 2/2] eal: clean up interrupt handle
Date: Tue, 4 Apr 2017 13:54:27 +0000	[thread overview]
Message-ID: <AM4PR05MB150553B8A1ADA3F161A1A07CC30B0@AM4PR05MB1505.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20170404212125.32114-3-qi.z.zhang@intel.com>

Wednesday, April 5, 2017 12:21 AM, Qi Zhang:
> The patch change the prototype of callback function
> (rte_intr_callback_fn) by removing the unnecessary parameter.
> 
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
> 
> v4:
> 
> - Update mlx5 driver which is missed in v1, v2, v3.

Thanks for the update of mlx5.
The compilation is still failing for mlx4. the implementation there is much similar to mlx5.

> 
> v3:
> 
> - Update bnx2x driver which is missed in v1,v2
> 
> v2:
> 
> - Seperate patch 1 of v1 into 2 patches.(part 2)
> 
>  drivers/net/bnx2x/bnx2x_ethdev.c               |  5 +++--
>  drivers/net/bnxt/bnxt_irq.c                    |  3 +--
>  drivers/net/e1000/em_ethdev.c                  |  8 +++-----
>  drivers/net/e1000/igb_ethdev.c                 | 15 ++++++---------
>  drivers/net/enic/enic_main.c                   |  3 +--
>  drivers/net/fm10k/fm10k_ethdev.c               | 12 ++++--------
>  drivers/net/i40e/i40e_ethdev.c                 |  8 +++-----
>  drivers/net/i40e/i40e_ethdev_vf.c              |  5 ++---
>  drivers/net/ixgbe/ixgbe_ethdev.c               | 14 +++++---------
>  drivers/net/mlx5/mlx5.h                        |  2 +-
>  drivers/net/mlx5/mlx5_ethdev.c                 |  3 +--
>  drivers/net/nfp/nfp_net.c                      |  6 ++----
>  drivers/net/qede/qede_ethdev.c                 |  4 ++--
>  drivers/net/sfc/sfc_intr.c                     | 10 ++++++----
>  drivers/net/virtio/virtio_ethdev.c             |  5 ++---
>  lib/librte_eal/common/include/rte_interrupts.h |  3 +--
>  lib/librte_eal/linuxapp/eal/eal_alarm.c        |  5 ++---
>  lib/librte_eal/linuxapp/eal/eal_interrupts.c   |  3 +--
>  18 files changed, 46 insertions(+), 68 deletions(-)

[...]

> @@ -119,12 +119,13 @@ bnx2x_interrupt_action(struct rte_eth_dev *dev)

  reply	other threads:[~2017-04-04 13:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31  2:09 [dpdk-dev] [PATCH v3 0/2] " 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 ` [dpdk-dev] [PATCH v3 0/2] clean up interrupt handle Thomas Monjalon
2017-04-04 12:41   ` 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 [this message]
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=AM4PR05MB150553B8A1ADA3F161A1A07CC30B0@AM4PR05MB1505.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.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).