From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org,
Peter Korsgaard <peter.korsgaard@barco.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3] i2c: i2c-mux-gpio: update mux with gpiod_set_array_value_cansleep
Date: Tue, 29 Nov 2016 20:15:02 +0100 [thread overview]
Message-ID: <20161129191502.GB10865@katana> (raw)
In-Reply-To: <1480011568-13254-1-git-send-email-peda@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
On Thu, Nov 24, 2016 at 07:19:28PM +0100, Peter Rosin wrote:
> If the gpio controller supports it and the gpio lines are concentrated
> to one gpio chip, the mux controller pins will get updated simultaneously.
>
> Signed-off-by: Peter Rosin <peda@axentia.se>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-11-29 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 18:19 [PATCH v3] i2c: i2c-mux-gpio: update mux with gpiod_set_array_value_cansleep Peter Rosin
2016-11-29 19:15 ` Wolfram Sang [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=20161129191502.GB10865@katana \
--to=wsa-dev@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=wsa@the-dreams.de \
/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).