From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"Nehal-Bakulchandra.Shah@amd.com"
<Nehal-Bakulchandra.Shah@amd.com>
Cc: "wsa@the-dreams.de" <wsa@the-dreams.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"Shyam-sundar.S-k@amd.com" <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH] i2c: designware: Fix regression when dynamic TAR update is disabled
Date: Fri, 10 Feb 2017 12:48:57 +0200 [thread overview]
Message-ID: <d1db459e-59a4-72d8-e21c-bb44545f10e6@linux.intel.com> (raw)
In-Reply-To: <110f9081-ddba-82c2-6ba3-f92bc36d0bc3@amd.com>
On 10.02.2017 08:38, Suravee Suthikulpanit wrote:
> At this points, my understanding is there are probably two options here:
>
> 1) Keep the commit 63d0f0a6952a (i2c: designware: detect when dynamic
> tar update
> is possible) and apply V2 of this patch in 4.10. We might need to
> back-port the change
> to v4.9 stable as well.
>
> 2) Revert the 63d0f0a6952a (i2c: designware: detect when dynamic tar
> update is possible) in 4.10,
> and also in v4.9 stable as well.
>
I'm fine with both options. Maybe revert as commit 0317e6c0f1dc ("i2c:
designware: do not disable adapter after transfer") was also reverted
and this revert doesn't seem to cause conflicts.
--
Jarkko
next prev parent reply other threads:[~2017-02-10 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:50 [PATCH] i2c: designware: Fix regression when dynamic TAR update is disabled Shah Nehal-Bakulchandra
2017-02-09 20:07 ` Andy Shevchenko
2017-02-09 21:34 ` De Marchi, Lucas
2017-02-10 6:38 ` Suravee Suthikulpanit
2017-02-10 10:48 ` Jarkko Nikula [this message]
2017-02-13 4:15 ` Shah, Nehal-bakulchandra
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=d1db459e-59a4-72d8-e21c-bb44545f10e6@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=Nehal-Bakulchandra.Shah@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mika.westerberg@linux.intel.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