All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stratos Psomadakis <psomas@ece.ntua.gr>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Subject: Re: [BUG] DMA_ERROR_CODE undefined in radeon_gart.c
Date: Tue, 19 Apr 2011 23:04:40 +0300	[thread overview]
Message-ID: <4DADEAD8.4090203@ece.ntua.gr> (raw)
In-Reply-To: <20110419194222.GA23953@gherkin.frus.com>

On 19/04/2011 10:42 μμ, Bob Tracy wrote:
> Attempted to build 2.6.39-rc4 on an Alpha and got the following error:
>
>   CC [M]  drivers/gpu/drm/radeon/radeon_gart.o
> drivers/gpu/drm/radeon/radeon_gart.c: In function 'radeon_gart_bind':
> drivers/gpu/drm/radeon/radeon_gart.c:186: error: 'DMA_ERROR_CODE' undeclared (first use in this function)
> drivers/gpu/drm/radeon/radeon_gart.c:186: error: (Each undeclared identifier is reported only once
> drivers/gpu/drm/radeon/radeon_gart.c:186: error: for each function it appears in.)
> make[4]: *** [drivers/gpu/drm/radeon/radeon_gart.o] Error 1
> make[3]: *** [drivers/gpu/drm/radeon] Error 2
> make[2]: *** [drivers/gpu/drm] Error 2
> make[1]: *** [drivers/gpu] Error 2
> make: *** [drivers] Error 2
>
> It appears that "DMA_ERROR_CODE" is currently defined for several
> architectures in "arch/*/include/asm/dma-mapping.h", but not for "alpha"
Similar issue in this discussion [1].
They solved it by replacing DMA_ERROR_CODE with dma_mapping_error().
Probably this can work here too.

-- 
Stratos Psomadakis
<psomas@ece.ntua.gr>


  reply	other threads:[~2011-04-19 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 19:42 [BUG] DMA_ERROR_CODE undefined in radeon_gart.c Bob Tracy
2011-04-19 20:04 ` Stratos Psomadakis [this message]
2011-04-19 20:07   ` Stratos Psomadakis

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=4DADEAD8.4090203@ece.ntua.gr \
    --to=psomas@ece.ntua.gr \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.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.