All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hinds <dhinds@sonic.net>
To: damjan@bagra.net.mk
Cc: linux-kernel@vger.kernel.org, trivial@rustcorp.com.au,
	dahinds@users.sourceforge.net
Subject: Re: Trivial patch for drivers/serial/8250_cs
Date: Mon, 25 Aug 2003 15:48:29 -0700	[thread overview]
Message-ID: <20030825154829.B20096@sonic.net> (raw)
In-Reply-To: <3F4A7F2C.7080205@bagra.net.mk>

On Mon, Aug 25, 2003 at 11:27:08PM +0200, ???????????? ?????????????????????? wrote:
> This patch is against 2.6.0-test4.
> It fixes the pcmcia serial driver to know its now called 8250_cs and not 
> serial_cs...
> 
> Without this patch 8250_cs compiles but doesn't work.

What do you mean by "doesn't work", exactly?  The existing name should
work if you have:

  device "serial_cs" module "8250_cs"

in /etc/pcmcia/config.  With your patch, it would work with:

  device "8250_cs" module "8250_cs"

(and also changing every instance of serial_cs to 8250_cs)

> All the patch does is change several "serial_cs" occurences to "8250_cs".
>
> PS.
> another possible sollution is to change everything (including the file 
> name) from "8250_cs" to "serial_cs" like it is in 2.4

I would say that "serial_cs" is more accurate since this is the driver
for cards that conform to the standard for PCMCIA serial interfaces.
Renaming to "8250_cs" is obfuscatory and pointlessly breaks config
files for previous kernel versions.  It is second in foolishness only
to the genious who thought renaming "ide_cs" to "ide-cs" was a good
idea.

-- Dave

P.S. -- your email name ('???...') is a good way to target your email
to the spam bucket; I almost discarded it myself.

  reply	other threads:[~2003-08-25 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 21:27 Trivial patch for drivers/serial/8250_cs Дамјан Георгиевски
2003-08-25 22:48 ` David Hinds [this message]
2003-08-26  0:15   ` 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=20030825154829.B20096@sonic.net \
    --to=dhinds@sonic.net \
    --cc=dahinds@users.sourceforge.net \
    --cc=damjan@bagra.net.mk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@rustcorp.com.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.