From: Linus Walleij <linus.walleij@linaro.org>
To: Rajmohan Mani <rajmohan.mani@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v3 2/3] gpio: Add support for TPS68470 GPIOs
Date: Tue, 20 Jun 2017 10:52:56 +0200 [thread overview]
Message-ID: <CACRpkdZU2kuBGh84DL8naHitoj3Y-pFXLyw5vec36fWMHLnyQA@mail.gmail.com> (raw)
In-Reply-To: <1497259612-38401-3-git-send-email-rajmohan.mani@intel.com>
On Mon, Jun 12, 2017 at 11:26 AM, Rajmohan Mani <rajmohan.mani@intel.com> wrote:
> This patch adds support for TPS68470 GPIOs.
> There are 7 GPIOs and a few sensor related GPIOs.
> These GPIOs can be requested and configured as
> appropriate.
>
> Signed-off-by: Rajmohan Mani <rajmohan.mani@intel.com>
This is some fine code.
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Feel free to merge this through MFD or tell me if I should
merge it if there are no compile-time dependencies.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-06-20 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 9:26 [PATCH v3 0/3] TPS68470 PMIC drivers Rajmohan Mani
2017-06-12 9:26 ` [PATCH v3 1/3] mfd: Add new mfd device TPS68470 Rajmohan Mani
2017-06-12 9:45 ` Andy Shevchenko
2017-06-12 10:06 ` Mani, Rajmohan
2017-06-18 21:46 ` kbuild test robot
2017-06-12 9:26 ` [PATCH v3 2/3] gpio: Add support for TPS68470 GPIOs Rajmohan Mani
2017-06-20 8:52 ` Linus Walleij [this message]
2017-06-20 22:16 ` Mani, Rajmohan
2017-06-12 9:26 ` [PATCH v3 3/3] ACPI / PMIC: Add TI PMIC TPS68470 operation region driver Rajmohan Mani
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=CACRpkdZU2kuBGh84DL8naHitoj3Y-pFXLyw5vec36fWMHLnyQA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajmohan.mani@intel.com \
--cc=rjw@rjwysocki.net \
/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).