linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Amit Shah <amit.shah@redhat.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: linux-next: Tree for Feb 13 (virtio_console)
Date: Thu, 14 Feb 2013 13:30:37 +1030	[thread overview]
Message-ID: <87sj4zk3ai.fsf@rustcorp.com.au> (raw)
In-Reply-To: <511BEC55.5090801@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> On 02/13/13 00:35, Stephen Rothwell wrote:
>> Hi all,
>> 
>> Changes since 20130212:
>
> on i386:
>
> drivers/built-in.o: In function `in_intr':
> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll'
> virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick'
> drivers/built-in.o: In function `resize_console':
> virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize'
> drivers/built-in.o: In function `unplug_port':
> virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove'
> drivers/built-in.o: In function `init_port_console':
> (.text+0x2fe59): undefined reference to `hvc_alloc'
> drivers/built-in.o: In function `virtio_cons_early_init':
> (.init.text+0x16d1): undefined reference to `hvc_instantiate'
>
>
> Full randconfig file is attached.

This looks like an impossible config.  CONFIG_VIRTIO_CONSOLE=y, but
CONFIG_HVC_DRIVER isn't set.

>From drivers/char/Kconfig:

        config VIRTIO_CONSOLE
        	tristate "Virtio console"
        	depends on VIRTIO
        	select HVC_DRIVER

???

Cheers,
Rusty.

  reply	other threads:[~2013-02-14  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13  8:35 linux-next: Tree for Feb 13 Stephen Rothwell
2013-02-13 19:41 ` linux-next: Tree for Feb 13 (virtio_console) Randy Dunlap
2013-02-14  3:00   ` Rusty Russell [this message]
2013-02-14  7:06     ` Stephen Rothwell
2013-02-14 18:45     ` Randy Dunlap
2013-02-14 18:55       ` Randy Dunlap
2013-02-14 23:55         ` Stephen Rothwell
2013-02-15  0:02           ` Greg KH
2013-02-15  0:23             ` Stephen Rothwell
2013-02-15  0:51               ` Joe Millenbach

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=87sj4zk3ai.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=amit.shah@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=virtualization@lists.linux-foundation.org \
    /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).