From: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
jslaby@suse.com, jay.dolan@accesio.com, hslester96@gmail.com,
je.yen.tam@ni.com, lkp@intel.com, kai.heng.feng@canonical.com,
heikki.krogerus@linux.intel.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, peter_hong@fintek.com.tw,
"Ji-Ze Hong (Peter Hong)" <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH V1 1/1] serial: 8250_pci: Add F81504A series Support
Date: Fri, 23 Aug 2019 09:26:58 +0800 [thread overview]
Message-ID: <b15b0504-91d3-a147-0613-5c8a4749e74d@gmail.com> (raw)
In-Reply-To: <20190822211511.GA11893@kroah.com>
Hi,
Greg KH 於 2019/8/23 上午 05:15 寫道:
>> Andy Shevchenko 於 2019/8/16 下午 07:26 寫道:
>>> We have 8250_fintek.
>>> Isn't it a right place to add these?
>>>
>>
>> The 8250_fintek implements PNP device with id PNP0501.
>> Should I also implements PCIe device in this file?
>
> Does it use the same logic? If so, that makes sense, but if you can not
> share anything, then no, it does not make sense.
>
It's same with old series F81504/508/512 and the old series had
implement in 8250_pci.c (pbn_fintek_4/pbn_fintek_8/pbn_fintek_12).
So I decide implements the new series in 8250_pci.c
Thanks
--
With Best Regards,
Peter Hong
prev parent reply other threads:[~2019-08-23 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 5:27 [PATCH V1 1/1] serial: 8250_pci: Add F81504A series Support Ji-Ze Hong (Peter Hong)
2019-08-16 11:26 ` Andy Shevchenko
2019-08-19 0:49 ` Ji-Ze Hong (Peter Hong)
2019-08-22 21:15 ` Greg KH
2019-08-23 1:26 ` Ji-Ze Hong (Peter Hong) [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=b15b0504-91d3-a147-0613-5c8a4749e74d@gmail.com \
--to=hpeter@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hpeter+linux_kernel@gmail.com \
--cc=hslester96@gmail.com \
--cc=jay.dolan@accesio.com \
--cc=je.yen.tam@ni.com \
--cc=jslaby@suse.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--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).