From: Linus Walleij <linus.walleij@linaro.org>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: 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>
Subject: Re: [PATCH v2 4/5] gpio: gpio-mm: Add support for GPIO names
Date: Wed, 1 Feb 2017 16:05:51 +0100 [thread overview]
Message-ID: <CACRpkdas=gWCU-OoiUzgmf+m+=8BC3BemPxj01a5F5w78e+vaQ@mail.gmail.com> (raw)
In-Reply-To: <3b487a6dcdc075d7fc0414911ec8133cdff46eb1.1485800977.git.vilhelm.gray@gmail.com>
On Mon, Jan 30, 2017 at 7:33 PM, William Breathitt Gray
<vilhelm.gray@gmail.com> wrote:
> This patch sets the gpio_chip names option with an array of GPIO line
> names that match the manual documentation for the Diamond Systems
> GPIO-MM. This should make it easier for users to identify which GPIO
> line corresponds to a respective GPIO pin on the device.
>
> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-02-01 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 18:32 [PATCH v2 0/5] gpio: Add support for GPIO names for several ISA_BUS_API drivers William Breathitt Gray
2017-01-30 18:32 ` [PATCH v2 1/5] gpio: 104-dio-48e: Add support for GPIO names William Breathitt Gray
2017-02-01 15:03 ` Linus Walleij
2017-01-30 18:33 ` [PATCH v2 2/5] gpio: 104-idi-48: " William Breathitt Gray
2017-02-01 15:04 ` Linus Walleij
2017-01-30 18:33 ` [PATCH v2 3/5] gpio: 104-idio-16: " William Breathitt Gray
2017-02-01 15:05 ` Linus Walleij
2017-01-30 18:33 ` [PATCH v2 4/5] gpio: gpio-mm: " William Breathitt Gray
2017-02-01 15:05 ` Linus Walleij [this message]
2017-01-30 18:33 ` [PATCH v2 5/5] gpio: ws16c48: " William Breathitt Gray
2017-02-01 15:06 ` Linus Walleij
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='CACRpkdas=gWCU-OoiUzgmf+m+=8BC3BemPxj01a5F5w78e+vaQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@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).