From: Johan Hovold <johan@kernel.org>
To: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
peter_hong@fintek.com.tw, hpeter+linux_kernel@gmail.com
Subject: Re: [PATCH V2 3/4] serial: f81232: implement break control
Date: Fri, 31 Aug 2018 12:13:15 +0200 [thread overview]
Message-ID: <20180831101315.GM28861@localhost> (raw)
In-Reply-To: <3f4bc3ff-1e72-54ee-1047-c69a0ff45771@gmail.com>
On Thu, Aug 30, 2018 at 09:55:46AM +0800, Ji-Ze Hong (Peter Hong) wrote:
> Hi Johan,
>
> This article is duplication with
> [PATCH V2 3/4] USB: serial: f81232: implement break control
> [PATCH V2 3/4] serial: f81232: implement break control
> (Title not start with USB token)
>
> Should I discard this PATCH_V2 series and re-send PATCH_V3 ?
> or could you discard the patch - serial: f81232: implement break control
> only ?
Yes, no problem, so no need to resend. But thanks for highlighting this.
I'll try to look at these next week.
Johan
next prev parent reply other threads:[~2018-08-31 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 1:47 [PATCH V2 0/4] Fintek F81232 driver improve and fix Ji-Ze Hong (Peter Hong)
2018-08-30 1:47 ` [PATCH V2 1/4] USB: serial: f81232: clear overrun flag Ji-Ze Hong (Peter Hong)
2018-09-05 14:39 ` Johan Hovold
2018-09-07 7:41 ` Ji-Ze Hong (Peter Hong)
2018-08-30 1:47 ` [PATCH V2 2/4] USB: serial: f81232: add high baud rate support Ji-Ze Hong (Peter Hong)
2018-08-30 1:47 ` [PATCH V2 3/4] serial: f81232: implement break control Ji-Ze Hong (Peter Hong)
2018-08-30 1:55 ` Ji-Ze Hong (Peter Hong)
2018-08-31 10:13 ` Johan Hovold [this message]
2018-08-30 1:47 ` [PATCH V2 3/4] USB: " Ji-Ze Hong (Peter Hong)
2018-09-05 14:41 ` Johan Hovold
2018-08-30 1:47 ` [PATCH V2 4/4] USB: serial: f81232: fix bulk_in/out size Ji-Ze Hong (Peter Hong)
2018-09-05 14:46 ` 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=20180831101315.GM28861@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=hpeter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter_hong@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;
as well as URLs for NNTP newsgroup(s).