From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, Spang Oliver <oliver.spang@siemens.com>
Subject: drivers/serial/Makefile
Date: Mon, 24 Mar 2003 16:52:50 +0100 [thread overview]
Message-ID: <200303241652.50213.duncan.sands@math.u-psud.fr> (raw)
The serial driver is now compiled as "8250", rather than
the traditional "serial" (Kconfig says "serial" as well).
Assuming this was a mistake in the Makefile, I went and
had a look, but my brain exploded. What exactly is this
intended to do?
All the best,
"Confused"
PS: 8250_gsc, 8250_pci can be compiled as modules in their
own right.
#
# Makefile for the kernel serial device drivers.
#
# $Id: Makefile,v 1.8 2002/07/21 21:32:30 rmk Exp $
#
serial-8250-y :=
serial-8250-$(CONFIG_GSC) += 8250_gsc.o
serial-8250-$(CONFIG_PCI) += 8250_pci.o
serial-8250-$(CONFIG_PNP) += 8250_pnp.o
obj-$(CONFIG_SERIAL_CORE) += core.o
obj-$(CONFIG_SERIAL_21285) += 21285.o
obj-$(CONFIG_SERIAL_8250) += 8250.o $(serial-8250-y)
obj-$(CONFIG_SERIAL_8250_CS) += 8250_cs.o
obj-$(CONFIG_SERIAL_8250_ACORN) += 8250_acorn.o
obj-$(CONFIG_SERIAL_ANAKIN) += anakin.o
obj-$(CONFIG_SERIAL_AMBA) += amba.o
obj-$(CONFIG_SERIAL_CLPS711X) += clps711x.o
obj-$(CONFIG_SERIAL_SA1100) += sa1100.o
obj-$(CONFIG_SERIAL_UART00) += uart00.o
obj-$(CONFIG_SERIAL_SUNCORE) += suncore.o
obj-$(CONFIG_SERIAL_SUNZILOG) += sunzilog.o
obj-$(CONFIG_SERIAL_SUNSU) += sunsu.o
obj-$(CONFIG_SERIAL_SUNSAB) += sunsab.o
obj-$(CONFIG_SERIAL_MUX) += mux.o
obj-$(CONFIG_SERIAL_68328) += 68328serial.o
obj-$(CONFIG_SERIAL_68360) += 68360serial.o
obj-$(CONFIG_SERIAL_COLDFIRE) += mcfserial.o
obj-$(CONFIG_V850E_NB85E_UART) += nb85e_uart.o
next reply other threads:[~2003-03-24 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 15:52 Duncan Sands [this message]
2003-03-24 16:15 ` drivers/serial/Makefile Russell King
2003-03-24 16:33 AW: drivers/serial/Makefile Spang Oliver
2003-03-24 16:41 ` drivers/serial/Makefile Russell King
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=200303241652.50213.duncan.sands@math.u-psud.fr \
--to=duncan.sands@math.u-psud.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.spang@siemens.com \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®