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,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Jonathan Kim <jonathankim@gctsemi.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dean ahn <deanahn@gctsemi.com>
Subject: Re: linux-next: Tree for Jul 29 (staging/gdm724x)
Date: Mon, 29 Jul 2013 10:04:41 -0700 [thread overview]
Message-ID: <51F6A0A9.5040702@infradead.org> (raw)
In-Reply-To: <20130729163906.7ba07f7c024ad364b2feb513@canb.auug.org.au>
On 07/28/13 23:39, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130726:
>
on i386:
# CONFIG_TTY is not set
ERROR: "tty_port_tty_get" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_port_close_end" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_register_driver" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_buffer_request_room" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "put_tty_driver" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_port_close_start" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_set_operations" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_port_init" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_insert_flip_string_fixed_flag" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_register_device" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_unregister_device" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_std_termios" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_unregister_driver" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "__tty_alloc_driver" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_flip_buffer_push" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_port_tty_set" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_wakeup" [drivers/staging/gdm724x/gdmtty.ko] undefined!
ERROR: "tty_port_block_til_ready" [drivers/staging/gdm724x/gdmtty.ko] undefined!
--
~Randy
next prev parent reply other threads:[~2013-07-29 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 6:39 linux-next: Tree for Jul 29 Stephen Rothwell
2013-07-29 17:04 ` Randy Dunlap [this message]
2013-07-29 19:28 ` linux-next: Tree for Jul 29 (staging/gdm724x) Greg Kroah-Hartman
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=51F6A0A9.5040702@infradead.org \
--to=rdunlap@infradead.org \
--cc=deanahn@gctsemi.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathankim@gctsemi.com \
--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;
as well as URLs for NNTP newsgroup(s).