From: Lee Jones <lee.jones@linaro.org>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] timberdale: Use pci_enable_msix_exact() instead of pci_enable_msix()
Date: Mon, 3 Mar 2014 18:04:43 +0800 [thread overview]
Message-ID: <20140303100132.GA10579@lee--X1> (raw)
In-Reply-To: <20140303093318.GB25705@dhcp-26-207.brq.redhat.com>
> > > > > Applied, thanks.
> > > >
> > > > I've reverted this patch, as it doesn't build othognally.
> > > >
> > > > drivers/mfd/timberdale.c:718:2:
> > > > error: implicit declaration of function ‘pci_enable_msix_exact’
> > > > [-Werror=implicit-function-declaration]
> > >
> > > I should have to clarify it I think. Do you build on top of 3.14-rc4?
> >
> > Not yet. Is the required patch in there?
>
> Yep - commit 302a252 ("PCI/MSI: Add pci_enable_msi_range() and
> pci_enable_msix_range()").
Okay, seems to work fine post-rebase.
Reapplied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-03-03 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:15 [PATCH] timberdale: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19 11:44 ` Lee Jones
2014-02-21 16:56 ` Alexander Gordeev
2014-02-21 16:58 ` [PATCH v2] timberdale: Use pci_enable_msix_exact() " Alexander Gordeev
2014-02-24 16:29 ` Lee Jones
2014-03-03 7:25 ` Lee Jones
2014-03-03 8:10 ` Alexander Gordeev
2014-03-03 9:26 ` Lee Jones
2014-03-03 9:33 ` Alexander Gordeev
2014-03-03 10:04 ` Lee Jones [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=20140303100132.GA10579@lee--X1 \
--to=lee.jones@linaro.org \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sameo@linux.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).