public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-serial@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] tty: 8250_dw: fix build error for CONFIG_SERIAL_8250=m
Date: Wed, 24 Aug 2011 16:45:16 +0200	[thread overview]
Message-ID: <201108241645.16377.arnd@arndb.de> (raw)
In-Reply-To: <1314169906-12958-1-git-send-email-jamie@jamieiles.com>

On Wednesday 24 August 2011, Jamie Iles wrote:
> Allow 8250_dw to be built as a module and export serial8250_handle_irq
> so that 8250 can still be built as a module.  This prevents the
> following build failure:
> 
> drivers/built-in.o: In function `dw8250_handle_irq':
> 8250_dw.c:(.text+0xcad9c): undefined reference to `serial8250_handle_irq'

I think this won't fix the bug that Stephen was reporting, it will only
make the error message go away but it won't work in the end: When
CONFIG_SERIAL_8250_DW is set to 'm', the declaration of
serial8250_use_designware_io now gets stubbed out from of_serial.ko,
meaning that the 8250_dw module becomes useless.

At the very least you also need to export the serial8250_use_designware_io
symbol and check for CONFIG_SERIAL_8250_DW_MODULE in the header.

When go go to such length, I think the approach I initially advocated
(making 8250_dw a standalone platform_driver like of_serial) will be
nicer.

Another alternative would be to link 8250_dw.o into 8250.ko, but that
requires renaming the module and will conflict with some of the other
changes I'm still planning to do with the 8250 driver.

	Arnd

  reply	other threads:[~2011-08-24 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  7:11 [PATCH] tty: 8250_dw: fix build error for CONFIG_SERIAL_8250=m Jamie Iles
2011-08-24 14:45 ` Arnd Bergmann [this message]
2011-08-24 14:54   ` Jamie Iles
2011-08-24 15:09     ` Greg KH
2011-08-24 15:12       ` Jamie Iles
2011-08-24 15:24   ` Jamie Iles
2011-08-24 16:14     ` Arnd Bergmann

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=201108241645.16377.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=greg@kroah.com \
    --cc=jamie@jamieiles.com \
    --cc=linux-serial@vger.kernel.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