All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Paul Mackerass <paulus@au.ibm.com>,
	David McCullough <davidm@snapgear.com>,
	Mikael Starvik <starvik@axis.com>
Subject: Re: [PATCH] Add removal schedule of register_serial/unregister_serial to appropriate file
Date: Sat, 25 Jun 2005 10:47:25 +0100	[thread overview]
Message-ID: <20050625104725.A16381@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050623142335.A5564@flint.arm.linux.org.uk>; from rmk+lkml@arm.linux.org.uk on Thu, Jun 23, 2005 at 02:23:35PM +0100

On Thu, Jun 23, 2005 at 02:23:35PM +0100, Russell King wrote:
> +What:	register_serial/unregister_serial
> +When:	December 2005
> +Why:	This interface does not allow serial ports to be registered against
> +	a struct device, and as such does not allow correct power management
> +	of such ports.  8250-based ports should use serial8250_register_port
> +	and serial8250_unregister_port instead.
> +Who:	Russell King <rmk@arm.linux.org.uk>

Ok, now that this is in, I guess I should arrange for register_serial &
co to throw a compiler warning.  However, this is non-trivial because
several other drivers declare this function:

drivers/macintosh/macserial.c:int register_serial(struct serial_struct *req)
drivers/macintosh/macserial.c:void unregister_serial(int line)
drivers/serial/68328serial.c:int register_serial(struct serial_struct *req)
drivers/serial/68328serial.c:void unregister_serial(int line)
drivers/serial/crisv10.c:register_serial(struct serial_struct *req)
drivers/serial/crisv10.c:void unregister_serial(int line)

Can folk who look after these drivers please comment on why these
functions are there.


Other places appear to have a prototype for these functions but do not
use them:

arch/xtensa/platform-iss/console.c:int register_serial(struct serial_struct*);
arch/xtensa/platform-iss/console.c:void unregister_serial(int);
drivers/char/amiserial.c:int register_serial(struct serial_struct *req);
drivers/char/amiserial.c:void unregister_serial(int line);

The patch which follows this message will remove these.


In terms of the use of these functions, this is the state of play as of
yesterday:

arch/frv/kernel/setup.c://      register_serial(&__frv_uart0);
arch/frv/kernel/setup.c://      register_serial(&__frv_uart1);
drivers/char/mwave/mwavedd.c:   return register_serial(&serial);
drivers/char/mwave/mwavedd.c:           unregister_serial(pDrvData->sLine);
drivers/misc/ibmasm/uart.c:     sp->serial_line = register_serial(&serial);
drivers/misc/ibmasm/uart.c:     unregister_serial(sp->serial_line);
drivers/net/ioc3-eth.c: register_serial(&req);
drivers/net/ioc3-eth.c: register_serial(&req);
drivers/parport/parport_serial.c:               line = register_serial (&serial_req);
drivers/parport/parport_serial.c:               unregister_serial (priv->line[i]);
drivers/serial/bast_sio.c:      return register_serial(&serial_req);
drivers/serial/bast_sio.c:              unregister_serial(port[0]);
drivers/serial/bast_sio.c:              unregister_serial(port[1]);

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

  parent reply	other threads:[~2005-06-25  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 13:23 [PATCH] Add removal schedule of register_serial/unregister_serial to appropriate file Russell King
2005-06-23 13:54 ` Andi Kleen
2005-06-23 14:03 ` Adrian Bunk
2005-06-23 16:24   ` Andi Kleen
2005-06-23 18:32   ` Andrew Morton
2005-06-23 21:38     ` Dave Airlie
2005-06-23 19:13   ` Horst von Brand
2005-06-25  2:42 ` Pavel Machek
2005-06-25  9:47 ` Russell King [this message]
2005-06-25  9:57   ` Russell King
2005-06-27  0:36   ` David McCullough
2005-06-27  9:30     ` Russell King
2005-07-14 19:33 ` Russell King
2005-08-12 17:30   ` Max Asbock
2005-08-15  8:42     ` 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=20050625104725.A16381@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=davidm@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@au.ibm.com \
    --cc=starvik@axis.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 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.