From: Wolfram Sang <wsa@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Evan Nimmo <Evan.Nimmo@alliedtelesis.co.nz>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
"jdelvare@suse.de" <jdelvare@suse.de>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset
Date: Mon, 14 Sep 2020 08:49:20 +0200 [thread overview]
Message-ID: <20200914064920.GA1088@ninjato> (raw)
In-Reply-To: <61c139a0-26fc-8cd1-0b54-b7cb9d9c0648@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
> I'm happy to route it to stable@ if you think it's worth it but I don't
> think there's a specific Fixes: reference that can be used. The current
> behavior appears to have been that way since before git (looks like we
> noticed in 2014 but it's taken me 6 years to nag people into sending
> their fixes upstream).
Better late than never :) Thanks for sending and the heads up. If you
don't need it for stable, then we should maybe not send it. It would be
nice for 9665 but we haven't tested it on 9564. But I'll let it be your
call.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-14 6:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:32 [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset Evan Nimmo
2020-09-09 8:23 ` Wolfram Sang
2020-09-09 20:39 ` Chris Packham
2020-09-11 19:45 ` Wolfram Sang
2020-09-13 21:23 ` Chris Packham
2020-09-14 6:49 ` Wolfram Sang [this message]
2020-09-14 20:50 ` Chris Packham
2020-09-14 8:50 ` Andy Shevchenko
2020-09-14 8:51 ` Andy Shevchenko
2020-09-14 10:42 ` Stephen Rothwell
2020-09-14 11:01 ` Andy Shevchenko
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=20200914064920.GA1088@ninjato \
--to=wsa@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Evan.Nimmo@alliedtelesis.co.nz \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@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).