From: Bjorn Helgaas <bhelgaas@google.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, dri-devel@lists.freedesktop.org,
Matthew Garrett <mjg@redhat.com>
Subject: Re: linux-next: Tree for Apr 17 (pci-sysfs.c and vga_switcheroo.c)
Date: Wed, 25 Apr 2012 10:37:26 -0600 [thread overview]
Message-ID: <CAErSpo56ddRZCG=5yqcEUBPZ1_x76=33xkv5x-46gcNgQCA0Qg@mail.gmail.com> (raw)
In-Reply-To: <4F8DB90A.8050504@xenotime.net>
On Tue, Apr 17, 2012 at 12:40 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On 04/16/2012 09:42 PM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20120416:
>
>
> When CONFIG_VGA_ARB is not enabled:
>
> drivers/built-in.o: In function `boot_vga_show':
> pci-sysfs.c:(.text+0x1060f): undefined reference to `vga_default_device'
>
>
> and
>
> drivers/built-in.o: In function `boot_vga_show':
> pci-sysfs.c:(.text+0x8cc2): undefined reference to `vga_default_device'
> drivers/built-in.o: In function `vga_switcheroo_register_client':
> (.text+0x76671): undefined reference to `vga_default_device'
> drivers/built-in.o: In function `vga_switchto_stage1':
> vga_switcheroo.c:(.text+0x767f4): undefined reference to `vga_set_default_device'
I assume this is related to 77b267c7549e3629ea55cf780aa3d474da7bc2d5
("vgaarb: Add support for setting the default video device") and that
Matthew will take care of whatever needs to be done (if it's not fixed
already).
Bjorn
next prev parent reply other threads:[~2012-04-25 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 4:42 linux-next: Tree for Apr 17 Stephen Rothwell
2012-04-17 18:40 ` linux-next: Tree for Apr 17 (pci-sysfs.c and vga_switcheroo.c) Randy Dunlap
2012-04-25 16:37 ` Bjorn Helgaas [this message]
2012-04-25 16:45 ` Matthew Garrett
2012-04-17 18:57 ` linux-next: Tree for Apr 17 (rcu) Randy Dunlap
2012-04-17 16:32 ` Paul E. McKenney
2012-04-17 20:14 ` 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='CAErSpo56ddRZCG=5yqcEUBPZ1_x76=33xkv5x-46gcNgQCA0Qg@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rdunlap@xenotime.net \
--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).