From: "Upinder Malhi (umalhi)" <umalhi@cisco.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"<linux-next@vger.kernel.org>" <linux-next@vger.kernel.org>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
"<linux-rdma@vger.kernel.org>" <linux-rdma@vger.kernel.org>,
"<roland@kernel.org>" <roland@kernel.org>,
"<hal.rosenstock@gmail.com>" <hal.rosenstock@gmail.com>
Subject: Re: randconfig build error with next-20131211, in drivers/infiniband/hw/usnic/usnic_uiom.c
Date: Thu, 19 Dec 2013 22:38:23 +0000 [thread overview]
Message-ID: <B13BFDDB-0C52-4A27-B47B-05F71CB696FC@cisco.com> (raw)
In-Reply-To: <52B350BC.8000903@infradead.org>
Randy,
This - http://www.spinics.net/lists/linux-rdma/msg18126.html- has fix for this. Once the patch goes into ib for-next tree, the problem will go away.
Upinder
On Dec 19, 2013, at 12:02 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 12/11/13 07:57, Jim Davis wrote:
>> Building with the attached random configuration file,
>>
>> drivers/infiniband/hw/usnic/usnic_uiom.c: In function
>> ‘usnic_uiom_attach_dev_to_pd’:
>> drivers/infiniband/hw/usnic/usnic_uiom.c:505:2: error: implicit declaration of f
>> unction ‘iommu_domain_has_cap’ [-Werror=implicit-function-declaration]
>> if (!iommu_domain_has_cap(pd->domain, IOMMU_CAP_CACHE_COHERENCY)) {
>> ^
>> cc1: some warnings being treated as errors
>> make[3]: *** [drivers/infiniband/hw/usnic/usnic_uiom.o] Error 1
>>
>
>
> This build error still happens in linux-next of 20131219.
>
> --
> ~Randy
prev parent reply other threads:[~2013-12-19 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:57 Jim Davis
2013-12-19 20:02 ` Randy Dunlap
2013-12-19 22:38 ` Upinder Malhi (umalhi) [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=B13BFDDB-0C52-4A27-B47B-05F71CB696FC@cisco.com \
--to=umalhi@cisco.com \
--cc=hal.rosenstock@gmail.com \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=roland@kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®