mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test5 vs. modem cards
Date: Sun, 14 Sep 2003 09:19:22 +0100	[thread overview]
Message-ID: <20030914091922.C20889@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1b7401c37a73$87b0e250$2dee4ca5@DIAMONDLX60>; from ndiamond@wta.att.ne.jp on Sun, Sep 14, 2003 at 12:51:36PM +0900

On Sun, Sep 14, 2003 at 12:51:36PM +0900, Norman Diamond wrote:
> In file 8250_cs.c:
> Line 61, identifies itself as "serial_cs.c" instead of "8250_cs.c".
> Line 119 identifies itself as "serial_cs" instead of "8250_cs".
> My partial understanding of Linux PCMCIA operations yields a guess that line
> 119 is part of the cause for failure during execution, whereas line 61 only
> potentially confuses future maintainers.

Its going to get renamed back to serial_cs shortly.

> Later in the same source file, calls to register_serial() and
> unregister_serial() compile but fail during execution.  Of course in order
> to make it execute in the first place I have to manually modprobe 8250_cs,
> because of the reason mentioned above.  /var/log/messages gets reports that
> those symbols are unknown.

I have no idea how you managed that.  The configuration subsystem does
not allow you to build 8250_cs.c as a module without building 8250.c in
some manner, and 8250.c provides those symbols.

-- 
Russell King (rmk@arm.linux.org.uk)	http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
  2.6 ARM Linux   - http://www.arm.linux.org.uk/
  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
  2.6 Serial core

  reply	other threads:[~2003-09-14  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-14  3:51 Norman Diamond
2003-09-14  8:19 ` Russell King [this message]
2003-09-14 10:44   ` Norman Diamond

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=20030914091922.C20889@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    /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®