public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: tmhikaru@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'serial' cannot be built as module
Date: Sat, 14 Jan 2006 09:29:25 +0000	[thread overview]
Message-ID: <20060114092925.GA9443@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060114092142.GA10844@roll>

On Sat, Jan 14, 2006 at 04:21:42AM -0500, tmhikaru@gmail.com wrote:
> I've already tried reporting this to the maintainer in the MAINTAINERS file,
> but received no response (mail originally sent 15'th of november)

My mail server has no record of this for the 15th - it never reached me.
Maybe you mis-copied the address?

> Essentially, the 'serial' module is not, apparently, being built when set as
> modular. I definitely know it's not being installed when I do make
> modules_install.
> 
> However, if I include it in the kernel, it works. The 'symbol' is SERIAL_8250
> according to the help in menuconfig.
> 
> I'd really like to have this fixed, as I try to reduce the size of the
> kernel that I boot, as I have to load the kernel off a floppy disk.

There's nothing which requires fixing.

If you read the help for that option, you will find that it's called
"8250" not "serial".  It also depends on serial_core.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-01-14  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14  9:21 'serial' cannot be built as module tmhikaru
2006-01-14  9:29 ` Russell King [this message]
     [not found]   ` <20060118112121.GA10343@roll>
     [not found]     ` <20060118113832.GB24960@flint.arm.linux.org.uk>
2006-01-19 10:34       ` [PATCH] serial: 8250 Documentation fix tmhikaru

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=20060114092925.GA9443@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmhikaru@gmail.com \
    /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