From: Oded Gabbay <oded.gabbay@amd.com>
To: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: randconfig build error with next-20141121, in drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c
Date: Fri, 21 Nov 2014 22:06:46 +0200 [thread overview]
Message-ID: <546F9B56.2010900@amd.com> (raw)
In-Reply-To: <CA+r1Zhj4+v+ggOhXm_3qz5=d8PgSDRexs1qQB9dk+KOC2TVzMA@mail.gmail.com>
On 11/21/2014 07:04 PM, Jim Davis wrote:
> Building with the attached random configuration file,
>
> drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c: In function ‘kfd_doorbell_init’:
> drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c:97:2: error: implicit
> declaration of function ‘ioremap’
> [-Werror=implicit-function-declaration]
> kfd->doorbell_kernel_ptr = ioremap(kfd->doorbell_base,
> ^
> drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c:97:27: warning: assignment
> makes pointer from integer without a cast [enabled by default]
> kfd->doorbell_kernel_ptr = ioremap(kfd->doorbell_base,
> ^
> drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c: In function ‘write_kernel_doorbell’:
> drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c:217:3: error: implicit declaration of
> function ‘writel’ [-Werror=implicit-function-declaration]
> writel(value, db);
> ^
> cc1: some warnings being treated as errors
> make[4]: *** [drivers/gpu/drm/amd/amdkfd/kfd_doorbell.o] Error 1
>
Thanks, I'm now sending a patch that fixes this problem.
Oded
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-11-21 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 17:04 randconfig build error with next-20141121, in drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c Jim Davis
2014-11-21 20:06 ` Oded Gabbay [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=546F9B56.2010900@amd.com \
--to=oded.gabbay@amd.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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;
as well as URLs for NNTP newsgroup(s).