From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-serial@vger.kernel.org, gnomes@lxorguk.ukuu.org.uk,
andy.shevchenko@gmail.com, Rob Groner <rgroner@rtd.com>
Subject: Re: [PATCH v5] serial: 8250: add gpio support to exar
Date: Sun, 7 Feb 2016 13:35:28 -0800 [thread overview]
Message-ID: <20160207213528.GA2018@kroah.com> (raw)
In-Reply-To: <56B74C87.3080301@gmail.com>
On Sun, Feb 07, 2016 at 07:24:15PM +0530, Sudip Mukherjee wrote:
> On Sunday 07 February 2016 12:14 PM, Greg Kroah-Hartman wrote:
> >On Tue, Jan 19, 2016 at 11:36:35AM +0530, Sudip Mukherjee wrote:
> >>Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which
> >>can be controlled using gpio interface.
> >>Add support to use these pins.
> >>
> >>Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> >>---
> >
> >I need an ack from the gpio maintainer before I can take this.
> >
> >Or was it going to be reworked again?
>
> I have not yet started with the rework, but Andy wants me to split out the
> exar related code from 8250_pci and create its own driver. But at the
> initial discussion you were against having a separate driver for it.
> what will you suggest?
I don't remember what my initial suggestion was at all, sorry. But I
like what Peter was doing with the other tty driver splitout, so that
might be the correct thing to do here.
thanks,
greg k-h
prev parent reply other threads:[~2016-02-07 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 6:06 [PATCH v5] serial: 8250: add gpio support to exar Sudip Mukherjee
2016-01-19 10:09 ` Andy Shevchenko
2016-01-19 11:14 ` Sudip Mukherjee
2016-01-19 11:39 ` Andy Shevchenko
2016-02-07 6:44 ` Greg Kroah-Hartman
2016-02-07 13:54 ` Sudip Mukherjee
2016-02-07 21:35 ` Greg Kroah-Hartman [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=20160207213528.GA2018@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gnurou@gmail.com \
--cc=jslaby@suse.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rgroner@rtd.com \
--cc=sudipm.mukherjee@gmail.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).