From: Peter Hung <hpeter@gmail.com>
To: johan@kernel.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, tom_tsai@fintek.com.tw,
peter_hong@fintek.com.tw,
Peter Hung <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH V3 1/1] usb:serial:f81534 add F81532/534 driver
Date: Fri, 10 Jul 2015 17:35:34 +0800 [thread overview]
Message-ID: <559F91E6.4030701@gmail.com> (raw)
In-Reply-To: <1436411737-27781-1-git-send-email-hpeter+linux_kernel@gmail.com>
Hi Johan,
Peter Hung 於 2015/7/9 上午 11:15 寫道:
> This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
>
Please pending for the driver, I found a problem with
prepare_write_buffer(). The driver submit write block size
!= real tx send size. It's will ok on transmitting small mount data,
but it's will fail on transmitting large mount data.
I'll fix for this problem and re-send patch.
Sorry for found bug so lately.
--
With Best Regards,
Peter Hung
next prev parent reply other threads:[~2015-07-10 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 3:15 [PATCH V3 1/1] usb:serial:f81534 add F81532/534 driver Peter Hung
2015-07-10 9:35 ` Peter Hung [this message]
2015-07-10 9:51 ` Johan Hovold
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=559F91E6.4030701@gmail.com \
--to=hpeter@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
--cc=tom_tsai@fintek.com.tw \
/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