From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
Cc: linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [Resend with Signed-off-by]: Add new FT232H chip to drivers/usb/serial/ftdi_sio.c
Date: Fri, 17 Jun 2011 21:15:24 +0400 [thread overview]
Message-ID: <4DFB8BAC.5080901@ru.mvista.com> (raw)
In-Reply-To: <19963.29455.319574.581029@elektron.ikp.physik.tu-darmstadt.de>
Hello.
Uwe Bonnes wrote:
> Hello,
Greetings shouldn't be a part of the patch description. Just omit them, for
the future.
> appended patch adds support for the new FTDI FT232H chip. This chip is a
> single channel version of the dual FT2232H/quad FT4232H, coming with it's
> own default PID 0x6014 (FT2232H uses the same PID 0x6010 like FT2232C,
> FT4232H has also it's own PID).
> The patch was checked on an UM232H module and a terminal program with TX/RX
> shorted to that typing in the terminal reproduced the characters. The patch
> was written against the running 2.6.37.6 kernel, but applies to git-head
> without errors.
The last sentence should really be placed after the --- tear line.
> Please review and let me know(CC) of any problems.
> Signed-off-by: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
> --
> Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de
> Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
> --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
> From 8a6a023dfc616a53bb1dd9b989d01276499ce6a4 Mon Sep 17 00:00:00 2001
> From: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
> Date: Fri, 17 Jun 2011 15:59:07 +0200
> Subject: Add new FT232H chip
The signature (if any) should be after the patch, not before. Now Greg will
have to hand edit your patch to remove it.
> ---
> drivers/usb/serial/ftdi_sio.c | 19 ++++++++++++++-----
> drivers/usb/serial/ftdi_sio.h | 3 ++-
> drivers/usb/serial/ftdi_sio_ids.h | 1 +
> 3 files changed, 17 insertions(+), 6 deletions(-)
> diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
> index 1627289..2e06b90 100644
> --- a/drivers/usb/serial/ftdi_sio.c
> +++ b/drivers/usb/serial/ftdi_sio.c
[...]
> @@ -1559,7 +1565,8 @@ static int create_sysfs_attrs(struct usb_serial_port *port)
> priv->chip_type == FT2232C ||
> priv->chip_type == FT232RL ||
> priv->chip_type == FT2232H ||
> - priv->chip_type == FT4232H)) {
> + priv->chip_type == FT4232H ||
> + priv->chip_type == FT232H)) {
> retval = device_create_file(&port->dev,
> &dev_attr_latency_timer);
> }
> @@ -1580,7 +1587,8 @@ static void remove_sysfs_attrs(struct usb_serial_port *port)
> priv->chip_type == FT2232C ||
> priv->chip_type == FT232RL ||
> priv->chip_type == FT2232H ||
> - priv->chip_type == FT4232H) {
> + priv->chip_type == FT4232H ||
> + priv->chip_type == FT232H) {
Please use tabs for indenting, like above. scripts/checkpatch.pl should have
warned you here...
WBR, Sergei
next prev parent reply other threads:[~2011-06-17 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 15:30 [Resend with Signed-off-by]: Add new FT232H chip to drivers/usb/serial/ftdi_sio.c Uwe Bonnes
2011-06-17 15:51 ` Greg KH
2011-06-17 17:15 ` Sergei Shtylyov [this message]
2011-06-17 17:25 ` Greg KH
2011-06-17 17:49 ` Sergei Shtylyov
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=4DFB8BAC.5080901@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=bon@elektron.ikp.physik.tu-darmstadt.de \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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