From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: linux-next: Tree for Feb 12 (drm_pci.c)
Date: Tue, 12 Feb 2013 08:06:00 -0800 [thread overview]
Message-ID: <511A6868.5010605@infradead.org> (raw)
In-Reply-To: <20130212160953.b80a57fec99e4bd9afb4b601@canb.auug.org.au>
On 02/11/13 21:09, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130211:
>
when CONFIG_PCI is not enabled (on x86_64):
CC [M] drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function 'pcie_capability_read_dword' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [drivers/gpu/drm/drm_pci.o] Error 1
--
~Randy
next prev parent reply other threads:[~2013-02-12 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 5:09 linux-next: Tree for Feb 12 Stephen Rothwell
2013-02-12 16:06 ` Randy Dunlap [this message]
2013-02-12 21:43 ` linux-next: Tree for Feb 12 (drm_pci.c) Bjorn Helgaas
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=511A6868.5010605@infradead.org \
--to=rdunlap@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--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