From: Johannes Thumshirn <johannes.thumshirn@men.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johannes Thumshirn <johannes.thumshirn@men.de>,
<linux-serial@vger.kernel.org>
Subject: Re: linux-next: Tree for May 14 (tty/serial/men_z135_uart.c)
Date: Thu, 15 May 2014 08:15:55 +0200 [thread overview]
Message-ID: <20140515061555.GA13254@jtlinux> (raw)
In-Reply-To: <53739A4E.2040009@infradead.org>
On Wed, May 14, 2014 at 09:31:10AM -0700, Randy Dunlap wrote:
> On 05/14/2014 01:26 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20140513:
> >
>
> on x86_64:
>
> CONFIG_SERIAL_CORE=m
> but SERIAL_MEN_Z135=y.
>
> drivers/built-in.o: In function `men_z135_remove':
> men_z135_uart.c:(.text+0x5bc53): undefined reference to `uart_remove_one_port'
> drivers/built-in.o: In function `men_z135_set_termios':
> men_z135_uart.c:(.text+0x5c3b5): undefined reference to `uart_get_baud_rate'
> men_z135_uart.c:(.text+0x5c415): undefined reference to `uart_update_timeout'
> drivers/built-in.o: In function `men_z135_handle_tx':
> men_z135_uart.c:(.text+0x5c8f4): undefined reference to `uart_write_wakeup'
> drivers/built-in.o: In function `men_z135_intr':
> men_z135_uart.c:(.text+0x5ce28): undefined reference to `uart_handle_dcd_change'
> men_z135_uart.c:(.text+0x5ce51): undefined reference to `uart_handle_cts_change'
> drivers/built-in.o: In function `men_z135_probe':
> men_z135_uart.c:(.text+0x5cf96): undefined reference to `uart_add_one_port'
> drivers/built-in.o: In function `men_z135_init':
> men_z135_uart.c:(.init.text+0x26e9): undefined reference to `uart_register_driver'
> men_z135_uart.c:(.init.text+0x2766): undefined reference to `uart_unregister_driver'
> drivers/built-in.o: In function `men_z135_exit':
> men_z135_uart.c:(.exit.text+0xe4): undefined reference to `uart_unregister_driver'
> make[1]: *** [vmlinux] Error 1
>
Hi Randy,
There is a not yet merged patch from Arnd Bergmann, which can be found here:
https://lkml.org/lkml/2014/4/29/529
I've just checked and it resolves the problem at my place, can you please
verify it as well.
Thanks,
Johannes
next prev parent reply other threads:[~2014-05-15 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 8:26 linux-next: Tree for May 14 Stephen Rothwell
2014-05-14 16:31 ` linux-next: Tree for May 14 (tty/serial/men_z135_uart.c) Randy Dunlap
2014-05-15 6:15 ` Johannes Thumshirn [this message]
2014-05-15 16:51 ` 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=20140515061555.GA13254@jtlinux \
--to=johannes.thumshirn@men.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rdunlap@infradead.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