From: Greg KH <greg@kroah.com>
To: Wen Xiong <wendyx@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [ patch 2/7] drivers/serial/jsm: new serial device driver
Date: Sun, 27 Feb 2005 22:37:57 -0800 [thread overview]
Message-ID: <20050228063757.GA23595@kroah.com> (raw)
In-Reply-To: <42225A04.7080505@us.ltcfwd.linux.ibm.com>
On Sun, Feb 27, 2005 at 06:38:44PM -0500, Wen Xiong wrote:
> diff -Nuar linux-2.6.9.orig/drivers/serial/jsm/jsm_tty.c linux-2.6.9.new/drivers/serial/jsm/jsm_tty.c
> --- linux-2.6.9.orig/drivers/serial/jsm/jsm_tty.c 1969-12-31 18:00:00.000000000 -0600
> +++ linux-2.6.9.new/drivers/serial/jsm/jsm_tty.c 2005-02-27 17:09:43.456960832 -0600
> @@ -0,0 +1,1273 @@
> +/*
> + * Copyright 2003 Digi International (www.digi.com)
> + * Scott H Kilau <Scott_Kilau at digi dot com>
But didn't you do a lot of work on this code too? Shouldn't you be
adding your copyright?
> + * NOTE TO LINUX KERNEL HACKERS: DO NOT REFORMAT THIS CODE!
> + *
> + * This is shared code between Digi's CVS archive and the
> + * Linux Kernel sources.
> + * Changing the source just for reformatting needlessly breaks
> + * our CVS diff history.
> + *
> + * Send any bug fixes/changes to: Eng.Linux at digi dot com.
> + * Thank you.
Is this still true? The formatting looks sane, so you can probably take
this all out. And put a real email address in there please...
> + * $Id: jsm_tty.c,v 1.79 2004/09/25 07:01:46 scottk Exp $
Take these out, not needed.
> +#include <linux/device.h> /* For udelay */
Comment is incorrect. What do you need device.h for?
> + DPR_IOCTL(("jsm_getmstat start\n"));
You have odd macros with two "((", what's up with that? Please use the
standard macros dev_dbg() and friends. It's a way to get a standard
message out of the kernel.
> +static void jsm_tty_set_mctrl(struct uart_port *port, unsigned int mctrl)
> +{
> + DPR_IOCTL(("jsm_set_modem_info() start\n"));
Oh, and why not just use __FUNCTION__?
> +static void jsm_tty_stop_rx(struct uart_port *port)
> +{
> +
> + JSM_CHANNEL->ch_bd->bd_ops->disable_receiver(JSM_CHANNEL);
> +
> +}
I think you can drop the extra lines here...
And what's with the all uppercase JSM_CHANNEL? Why not just use the
structure pointer.
thanks,
greg k-h
next prev parent reply other threads:[~2005-02-28 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 23:38 [ patch 2/7] drivers/serial/jsm: new serial device driver Wen Xiong
2005-02-28 0:25 ` Jeff Garzik
2005-02-28 6:37 ` Greg KH [this message]
2005-03-04 21:07 ` Wen Xiong
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=20050228063757.GA23595@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=wendyx@us.ibm.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