linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: china_shenglong <china_shenglong@163.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	johan@kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Wang Sheng Long <shenglong.wang.ext@siemens.com>
Subject: Re: [PATCH] usb-serial:cp210x: add support to software flow control
Date: Wed, 19 Aug 2020 10:19:31 +0200	[thread overview]
Message-ID: <415e7692-7452-41bb-ec7a-e80c42aa8507@siemens.com> (raw)
In-Reply-To: <386a30c0.ac88.1739eda0ee5.Coremail.china_shenglong@163.com>

On 30.07.20 10:32, china_shenglong wrote:
> Hi, Greg
> 
> Yeah, It mainly adjusts the code style according to the kernel
> specification,
> and then modifies it according to your previous review comments.
> 
> Thanks,
> 
> BR/ Wang ShengLong
> 
> 
> At 2020-07-30 16:06:39, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>>On Thu, Jul 30, 2020 at 03:59:22PM +0800, Sheng Long Wang wrote:
>>> From: Wang Sheng Long <shenglong.wang.ext@siemens.com>
>>> 
>>> When data is transmitted between two serial ports,
>>> the phenomenon of data loss often occurs. The two kinds
>>> of flow control commonly used in serial communication
>>> are hardware flow control and software flow control.
>>> 
>>> In serial communication, If you only use RX/TX/GND Pins, you
>>> can't do hardware flow. So we often used software flow control
>>> and prevent data loss. The user sets the software flow control
>>> through the application program, and the application program
>>> sets the software flow control mode for the serial port
>>> chip through the driver.
>>> 
>>> For the cp210 serial port chip, its driver lacks the
>>> software flow control setting code, so the user cannot set
>>> the software flow control function through the application
>>> program. This adds the missing software flow control.
>>> 
>>> Signed-off-by: Wang Sheng Long <shenglong.wang.ext@siemens.com>
>>> ---
>>>  drivers/usb/serial/cp210x.c | 118 ++++++++++++++++++++++++++++++++++--
>>>  1 file changed, 113 insertions(+), 5 deletions(-)
>>
>>What changed from the previous version of this patch?  That should be
>>described below the --- line and this is a v2, right?
>>
>>thanks,
>>
>>greg k-h

This no longer applies. Shenglong, could you send a rebased version as v3?
Please also include a changelog after the "---" separator this time.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      parent reply	other threads:[~2020-08-19  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  7:59 [PATCH] usb-serial:cp210x: add support to software flow control Sheng Long Wang
2020-07-30  8:06 ` Greg KH
     [not found]   ` <386a30c0.ac88.1739eda0ee5.Coremail.china_shenglong@163.com>
2020-08-18  8:50     ` Greg KH
2020-08-19  8:19     ` Jan Kiszka [this message]

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=415e7692-7452-41bb-ec7a-e80c42aa8507@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=china_shenglong@163.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shenglong.wang.ext@siemens.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;
as well as URLs for NNTP newsgroup(s).