From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, David Airlie <airlied@linux•ie>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
dri-devel@lists•freedesktop.org
Subject: Re: linux-next: Tree for July 8 (nouveau)
Date: Thu, 8 Jul 2010 09:48:42 -0700 [thread overview]
Message-ID: <20100708094842.2753a194.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100708151022.d2517577.sfr@canb.auug.org.au>
On Thu, 8 Jul 2010 15:10:22 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100707:
>
> The i.MX tree mismerge has been fixed.
>
> The omap tree gained a conflict (involving serveral files) against the
> arm tree.
>
> ----------------------------------------------------------------------------
Should nouveau depend on PCI?
It has build errors when PCI is disabled:
drivers/gpu/drm/nouveau/nouveau_bios.c: In function 'load_vbios_pci':
drivers/gpu/drm/nouveau/nouveau_bios.c:167: error: implicit declaration of function 'pci_enable_rom'
drivers/gpu/drm/nouveau/nouveau_bios.c:171: error: implicit declaration of function 'pci_map_rom'
drivers/gpu/drm/nouveau/nouveau_bios.c:171: warning: assignment makes pointer from integer without a cast
drivers/gpu/drm/nouveau/nouveau_bios.c:175: error: implicit declaration of function 'pci_unmap_rom'
drivers/gpu/drm/nouveau/nouveau_bios.c:178: error: implicit declaration of function 'pci_disable_rom'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-07-08 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 5:10 linux-next: Tree for July 8 Stephen Rothwell
2010-07-08 16:48 ` Randy Dunlap [this message]
2010-07-08 21:49 ` linux-next: Tree for July 8 (nouveau) Dave Airlie
2010-07-08 17:06 ` linux-next: Tree for July 8 (staging/spectra) Randy Dunlap
2010-07-08 20:55 ` [PATCH -next] tracing: writeback.h needs device.h Randy Dunlap
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=20100708094842.2753a194.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=airlied@linux$(echo .)ie \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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