From: Johan Hovold <johan@kernel.org>
To: Charles Yeh <charlesyeh522@gmail.com>
Cc: Rong Chen <rong.a.chen@intel.com>,
kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, gregkh@linuxfoundation.org,
Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org
Subject: Add Prolific new chip: PL2303TB & PL2303N(G)
Date: Thu, 3 Jan 2019 09:46:05 +0100 [thread overview]
Message-ID: <20190103084605.GC5620@localhost> (raw)
On Wed, Jan 02, 2019 at 10:52:46AM +0800, Charles Yeh wrote:
> Hi Rong Chen,
> Thank you for your expained.
>
> Hi Johan & Greg,
> Is this patch already OK?
I haven't had time to review your v2 yet due to holidays and merge
window. Will let you know.
Johan
next reply other threads:[~2019-01-03 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 8:46 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-02 2:52 Add Prolific new chip: PL2303TB & PL2303N(G) Charles Yeh
2019-01-02 1:45 kernel test robot
2019-01-02 1:04 Charles Yeh
2018-12-25 15:38 kbuild test robot
2018-12-25 14:00 Charles Yeh
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=20190103084605.GC5620@localhost \
--to=johan@kernel.org \
--cc=charlesyeh522@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rong.a.chen@intel.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).