All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, santosh <santosh.shukla@caviumnetworks.com>,
	ferruh.yigit@intel.com
Subject: Re: [PATCH] igb_uio: remove compilation warning on arm64 kernel
Date: Sun, 08 Oct 2017 17:19:43 +0200	[thread overview]
Message-ID: <4207002.sFuXJid24B@xps> (raw)
In-Reply-To: <86245f32-2a14-87cd-297b-6a53e82fcec2@caviumnetworks.com>

08/10/2017 12:59, santosh:
> 
> On Sunday 08 October 2017 02:47 PM, Hemant Agrawal wrote:
> > IGB_UIO compilation recently got enabled for ARM64 by default
> >
> > The igb_uio compilation against ARM64 based stock 4.x (e.g. 4.13)
> > kernel is giving compilation warnings:
> >
> > igb_uio.c: In function ‘igbuio_pci_irqcontrol’:
> > igb_uio.c:115:25: error: implicit declaration of function
> > ‘irq_get_irq_dat ’ [-Werror=implicit-function-declaration]
> >   struct irq_data *irq = irq_get_irq_data(udev->info.irq);
> >                          ^
> > igb_uio.c:115:25: error: initialization makes pointer from integer without
> > a cast [-Werror=int-conversion]
> >
> > Fixes: d196343a258e ("igb_uio: use kernel functions for masking MSI-X")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > ---
> 
> Breaks thunderx too.
> 
> Reviewed-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
> and
> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>

Applied, thanks

      reply	other threads:[~2017-10-08 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08  9:17 [PATCH] igb_uio: remove compilation warning on arm64 kernel Hemant Agrawal
2017-10-08 10:59 ` santosh
2017-10-08 15:19   ` Thomas Monjalon [this message]

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=4207002.sFuXJid24B@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=santosh.shukla@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.