From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci
Date: Mon, 06 Feb 2017 22:04:49 +0000 [thread overview]
Message-ID: <5898F301.60202@gmail.com> (raw)
In-Reply-To: <82b6d515-7ac8-5593-e4e7-d694612f94c1@siemens.com>
On Monday 06 February 2017 02:45 PM, Jan Kiszka wrote:
> On 2017-01-30 23:28, Sudip Mukherjee wrote:
>> From: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
>>
>> Add the serial driver for the Exar chips. And also register the
>> platform device for the GPIO provided by the Exar chips.
>>
>
> And another question: you left pci_fastcom335_setup and related things
> untouched - did that code come later, or is it left in 8250_pci.c for a
> reason?
That was discussed.
Those are separate chips from different vendor and this patchset was
specifically for Exar chips. So i suggested I will do it via separate patch.
Regards
Sudip
next prev parent reply other threads:[~2017-02-06 22:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 22:28 [PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci Sudip Mukherjee
2017-01-30 22:28 ` [PATCH v13 2/2] serial: 8250_pci: remove exar code Sudip Mukherjee
2017-02-03 14:02 ` [PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci Jan Kiszka
2017-02-03 14:08 ` Andy Shevchenko
2017-02-03 21:31 ` Sudip Mukherjee
2017-02-04 14:51 ` Andy Shevchenko
2017-02-06 13:49 ` Jan Kiszka
2017-02-06 14:06 ` Greg Kroah-Hartman
2017-02-06 14:20 ` Jan Kiszka
2017-02-06 22:07 ` Sudip Mukherjee
2017-02-06 22:13 ` Sudip Mukherjee
2017-02-06 14:45 ` Jan Kiszka
2017-02-06 22:04 ` Sudip Mukherjee [this message]
2017-02-07 10:09 ` Jan Kiszka
2017-02-06 19:37 ` Jan Kiszka
2017-02-06 19:47 ` Jan Kiszka
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=5898F301.60202@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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).