From: Jamie Iles <jamie@jamieiles.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Hoan Tran <hotran@apm.com>, Jamie Iles <jamie@jamieiles.com>,
Weike Chen <alvin.chen@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Loc Ho <lho@apm.com>, Duc Dang <dhdang@apm.com>
Subject: Re: [PATCH] gpio: dwapb: Add support for next generation of X-Gene SoC
Date: Mon, 13 Feb 2017 09:38:34 +0000 [thread overview]
Message-ID: <20170213093834.GA16603@page> (raw)
In-Reply-To: <CACRpkdZw-QLOeiPqSRaEJ+mGGDwi5fh9B1uenPxQGBtTwj+cuw@mail.gmail.com>
Hi Linus,
On Mon, Feb 06, 2017 at 11:21:09AM +0100, Linus Walleij wrote:
> On Tue, Jan 31, 2017 at 8:43 PM, Hoan Tran <hotran@apm.com> wrote:
>
> > Next generation of X-Gene SoC's GPIO hardware register map is very
> > similar to DW GPIO. It only differs by a few register addresses.
> > This patch modifies DW GPIO driver to accommodate the difference
> > in a few register addresses.
> >
> > Signed-off-by: Hoan Tran <hotran@apm.com>
>
> On next iteration please include Jamie Iles, Weike Chen and Sebastian
> Andrzej Siewior.
> They all provided substantial contributions to this driver.
>
> The dwapb needs a proper maintainer in MAINTAINERS actually, it is one of
> those that can't use GPIOLIB_IRQCHIP so it requires special attention.
> Jamie, interested in the job? Patches welcome :)
I actually don't have access to hardware using this driver anymore so
I'm probably not the right person for the job, but still happy to review
patches!
Jamie
next prev parent reply other threads:[~2017-02-13 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 19:43 [PATCH] gpio: dwapb: Add support for next generation of X-Gene SoC Hoan Tran
2017-02-02 19:47 ` Andy Shevchenko
2017-02-03 1:18 ` Hoan Tran
2017-02-06 10:21 ` Linus Walleij
2017-02-06 23:49 ` Hoan Tran
2017-02-07 9:18 ` Andy Shevchenko
2017-02-13 9:38 ` Jamie Iles [this message]
2017-02-15 1:22 ` Hoan Tran
2017-02-15 11:20 ` Jamie Iles
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=20170213093834.GA16603@page \
--to=jamie@jamieiles.com \
--cc=alvin.chen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=dhdang@apm.com \
--cc=gnurou@gmail.com \
--cc=hotran@apm.com \
--cc=lho@apm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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).