From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, Alex Hemme <ahemme@cisco.com>,
Wolfram Sang <wsa@the-dreams.de>, MakeB <mabnhdev@gmail.com>,
linux-i2c@vger.kernel.org, stable@vger.kernel.org,
Ziyang Wu <ziywu@cisco.com>
Subject: Re: [PATCH] i2c: i2c-mux-pca954x: fix deselect enabling for device-tree
Date: Sat, 19 Nov 2016 21:49:58 +0100 [thread overview]
Message-ID: <20161119204958.GA2856@katana> (raw)
In-Reply-To: <1479548918-21006-1-git-send-email-peda@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Sat, Nov 19, 2016 at 10:48:38AM +0100, Peter Rosin wrote:
> From: Alex Hemme <ahemme@cisco.com>
>
> Deselect functionality can be ignored for device-trees with
> "i2c-mux-idle-disconnect" entries if no platform_data is available.
> By enabling the deselect functionality outside the platform_data
> block the logic works as it did in previous kernels.
>
> Fixes: 7fcac9807175 ("i2c: i2c-mux-pca954x: convert to use an explicit i2c mux core")
> Cc: <stable@vger.kernel.org> # v4.7+
> Signed-off-by: Alex Hemme <ahemme@cisco.com>
> Signed-off-by: Ziyang Wu <ziywu@cisco.com>
> [touched up a few minor issues /peda]
> Signed-off-by: Peter Rosin <peda@axentia.se>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-11-19 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 9:48 [PATCH] i2c: i2c-mux-pca954x: fix deselect enabling for device-tree Peter Rosin
2016-11-19 20:49 ` 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=20161119204958.GA2856@katana \
--to=wsa-dev@sang-engineering.com \
--cc=ahemme@cisco.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mabnhdev@gmail.com \
--cc=peda@axentia.se \
--cc=stable@vger.kernel.org \
--cc=wsa@the-dreams.de \
--cc=ziywu@cisco.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).