[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1db459e-59a4-72d8-e21c-bb44545f10e6@linux.intel.com>
Date: Fri, 10 Feb 2017 12:48:57 +0200
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>,
"De Marchi, Lucas" <lucas.demarchi@...el.com>,
"mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
"andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>,
"Nehal-Bakulchandra.Shah@....com" <Nehal-Bakulchandra.Shah@....com>
Cc: "wsa@...-dreams.de" <wsa@...-dreams.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"Shyam-sundar.S-k@....com" <Shyam-sundar.S-k@....com>
Subject: Re: [PATCH] i2c: designware: Fix regression when dynamic TAR update
is disabled
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
Powered by blists - more mailing lists