All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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, 07 Feb 2016 19:24:15 +0530	[thread overview]
Message-ID: <56B74C87.3080301@gmail.com> (raw)
In-Reply-To: <20160207064407.GA24131@kroah.com>

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?

regards
sudip

  reply	other threads:[~2016-02-07 13:54 UTC|newest]

Thread overview: 9+ 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 10:09   ` Andy Shevchenko
2016-01-19 11:14   ` Sudip Mukherjee
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 [this message]
2016-02-07 21:35     ` Greg Kroah-Hartman

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=56B74C87.3080301@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gnurou@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.